RE: [nslu2-general] FSCK problem
- So how can I FSCK filesystem? I mean about cron based routine to
periodically run FSCK on whole HDD attached to USB port. Can anybody help
From: email@example.com [mailto:firstname.lastname@example.org]
On Behalf Of Marcel Nijenhof
Sent: Saturday, November 03, 2007 6:22 PM
Subject: Re: [nslu2-general] FSCK problem
On Sat, 2007-11-03 at 11:11 +0000, mackowiakp wrote:
> During running find utility on NSLU2 I got an error. I try to run
> manualny fsck from UNSLUNG console. There is result of fsck errors:
> -bash-3.2# find / -name Thumbs.db -print
> find: Filesystem loop detected; `/share/hdd/data' has the same device
> number and inode as a directory which is 3 levels higher in the
> filesystem hierarchy.
This really is one of those things where unslung does strange things.
The linksys software requires that the disk is mounted as
"/share/hdd/data" but we also use it as root disk so it's also
mounted as "/".
> -bash-3.2# fsck.ext3
> Segmentation fault
Did you try "fsck.ext3 -nf /dev/sdb1"?
The "-fn" is for forcing it to run on a mounted filesystem
with the "no change" option.
Never run fsck on a mounted filesystem and correct the errors
because after the next buffer sync from your os the filesystem
is corrupt and probably can't be repaired.
And yes fsck shouldn't crash if you don't give the correct
options so it's still a bug.
[Non-text portions of this message have been removed]