> I'd rather donate for a reiser4 online repacker. By the time
> something's fsck'd, so to speak, I'd rather take it offline and possibly
> pull in backups. But a repacker (even an offine one) and a resizer
> (even an offline one) are two things that we even have in the Linux
> ntfs-tools, and it
r[fs,4] to honour option
> processing in a manner more consistant with
> the other fscks, so that adding reiserfs to a list of user choosable
> filesystems is not going to cause a nightmare
> of an overhead of filesystem detection, command option re-mapping and
> other related headac
Is there or was there a plan to support running reiserfsck on a
mounted v3 filesystem (just a check, not a fix or rebuild)? I seem to
remember this being mentioned here at some point in time, but I was
unable to find it in the mailing list archive.
Thanks!
I posted this kernel panic once before and received no response. Now I
have another occurence and I need to find out what is happening:
vs-6030: check_internal_block_head: invalid item number level=2,
nr_items=211, free_space=64536 rdkey kernel BUG at prints.c:334!
invalid operand: 2.4.21-241
We are seeing this message preceeding a kernel panic:
Feb 5 16:29:43 rcs02 kernel: vs-6030: check_internal_block_head:
invalid item number level=2, nr_items=172, free_space=65472 rdkey
kernel BUG at prints.c:334!
We have run reiserfsck on all filesystems and found no errors. Can
someone elaborat
