From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: emerge error
Date: Wed, 23 Jan 2008 23:32:41 +0000 [thread overview]
Message-ID: <20080123233241.71bce684@zaphod.digimed.co.uk> (raw)
In-Reply-To: <loom.20080123T194909-645@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
On Wed, 23 Jan 2008 20:08:00 +0000 (UTC), James wrote:
> > No, because it will copy the corruption too. You'll end up with a byte
> > for byte copy of your broken filesystem. If fsck won't fix it, backup,
> > reformat, restore is the only safe fix.
> If I reboot, I *may* loose the firewall completely, depending on what
> the drive does. The only safe thing is to build another firewall before
> rebooting the current firewall (then see if fsck will fix it).......
Then don't reboot. Mount another drive somewhere temporary, copy the
contents of /var to it, then unmount /var and mount the new drive
on /var. Reformat the original filesystem and reverse the process.
> Either way, once I build a new firewall, I'm going to copy it
> to CF and be done with these old ide drives.........
Use a suitable filesystem, or the flash memory will die very quickly,
especially if you put /var on it.
--
Neil Bothwick
New Intel opcode #007 PUKE: Put unmeaningful keywords everywhere
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-01-23 23:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 3:08 [gentoo-user] emerge error James
2008-01-23 5:58 ` James Ausmus
2008-01-23 7:41 ` KH
2008-01-23 16:03 ` [gentoo-user] " James
2008-01-23 16:13 ` James Ausmus
2008-01-23 16:29 ` James
2008-01-23 16:39 ` James
2008-01-23 16:49 ` Neil Bothwick
2008-01-23 18:33 ` James
2008-01-23 19:37 ` Neil Bothwick
2008-01-23 20:08 ` James
2008-01-23 23:32 ` Neil Bothwick [this message]
2008-01-24 3:33 ` Hal Martin
2008-01-24 13:46 ` James
2008-01-24 20:07 ` Neil Bothwick
2008-01-25 1:34 ` James
2008-01-24 5:12 ` Joseph
2008-01-23 16:31 ` Dale
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080123233241.71bce684@zaphod.digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox