Hello
On Wed, 2005-04-27 at 21:19, Todd Curry wrote:
> Gang, I’m new to ReiserFS and admittedly clueless about filesystems.
> I’ve been happily easing into Linux for about a year, until we went
> RAID and LVM and suddenly I need to know things that: (a) I didn’t
> before, and (b) are a bit more arcane than I’m used to. I’ve googled
> and read man pages extensively, but I’m hitting diminishing returns
> for a fairly simple question / problem.
>
>
>
> Situation: unable to run reiserfsck on my reiser partition, which has
> what appears to be an error message while running debugreiserfs: This
> filesystem is NOT clean. No other errors, drive appears to be
> functioning normally. I’d like to ensure it is clean as a whistle,
> however.
>
>
>
> I’m running a simple RAID 5 setup as follows
>
>
>
> sda
>
> /boot == ext3
>
> Lvm…
>
>
>
> On lvm
>
> / == ext3
>
> /lvm == reiserfs (3, not 4)
>
>
>
>
>
> So, I tried umounting the /dev/lvmname/lvmX partition and get the
> “device busy” error
>
You can try to mount -o remount,ro and reiserfsck it.
If you can not even remount it readonly - you have to boot of rescue CD,
active lvm, and reiserfsck.
If you can not do that either
find /reiserfs-mount-point -type f -exec cat {} > /dev/null \;
if it works without problems - filesystem has reasonable consistency
>
>
> I’d like to find a way to run reiserfsck at boot either while I’m
> watching or log the output. I’m running Fedora Core 2. Any
> suggestions on how best to do this?
>
>
>
> Thanks,
>
>
>
> Todd
>
>
>
> Output from debugresiserfs below, for any experts who might see a
> problem…
>
>
>
> [EMAIL PROTECTED] fcdrive]# debugreiserfs /dev/currylvm/lvm03
>
> debugreiserfs 3.6.19 (2003 www.namesys.com)
>
>
>
>
>
> Filesystem state: consistency is not checked after last mounting
>
As long as filesystem is mounted - it is ok.
>
>
> Reiserfs super block in block 16 on 0xfd01 of format 3.6 with standard
> journal
>
> Count of blocks on the device: 115572736
>
> Number of bitmaps: 3527
>
> Blocksize: 4096
>
> Free blocks (count of blocks - used [journal, bitmaps, data, reserved]
> blocks): 58330605
>
> Root block: 23098989
>
> Filesystem is NOT clean
>
As long as filesystem is mounted - it is ok.
> Tree height: 5
>
> Hash function used to sort names: "r5"
>
> Objectid map size 2, max 972
>
> Journal parameters:
>
> Device [0x0]
>
> Magic [0x4e42afa0]
>
> Size 8193 blocks (including 1 for journal header) (first block
> 18)
>
> Max transaction length 1024 blocks
>
> Max batch size 900 blocks
>
> Max commit age 30
>
> Blocks reserved by journal: 0
>
> Fs state field: 0x0:
>
> sb_version: 2
>
> inode generation number: 1695433
>
> UUID: e38d4ba5-0c05-4e3c-92e5-ba714062622c
>
> LABEL:
>
> Set flags in SB:
>
> ATTRIBUTES CLEAN
>
>
