| 1 |
On Wed, 23 Jan 2008 20:08:00 +0000 (UTC), James wrote: |
| 2 |
|
| 3 |
> > No, because it will copy the corruption too. You'll end up with a byte |
| 4 |
> > for byte copy of your broken filesystem. If fsck won't fix it, backup, |
| 5 |
> > reformat, restore is the only safe fix. |
| 6 |
|
| 7 |
> If I reboot, I *may* loose the firewall completely, depending on what |
| 8 |
> the drive does. The only safe thing is to build another firewall before |
| 9 |
> rebooting the current firewall (then see if fsck will fix it)....... |
| 10 |
|
| 11 |
Then don't reboot. Mount another drive somewhere temporary, copy the |
| 12 |
contents of /var to it, then unmount /var and mount the new drive |
| 13 |
on /var. Reformat the original filesystem and reverse the process. |
| 14 |
|
| 15 |
> Either way, once I build a new firewall, I'm going to copy it |
| 16 |
> to CF and be done with these old ide drives......... |
| 17 |
|
| 18 |
Use a suitable filesystem, or the flash memory will die very quickly, |
| 19 |
especially if you put /var on it. |
| 20 |
|
| 21 |
|
| 22 |
-- |
| 23 |
Neil Bothwick |
| 24 |
|
| 25 |
New Intel opcode #007 PUKE: Put unmeaningful keywords everywhere |
Archives