jfs and ESTALE

[Andrey Vul]

How come, during fs corruption, some files on a jfs volume, ESTALE on
access? Does the fs mark dirty inodes  in need of fsck  and ESTALES
access until a consistent state is available?
Also, is there a way to disable the kernel from guessing the rootfs
type by explicitly specificying the fstype? Suppose the primary
superblock is damaged but the the other ones are all fine and mount -o
ro -t jfs succeeds. There  are times when I just don't want to fuck
with a livecd just to fsck / so that int mounts and init can run. Is
there a way to go from:
determine_fs_type
bad primay superblock
panic

to:
determine_fs_type
bad primary superblock
get fstype from cmdline
use alt superblock
run init
?

The discussion of alt superblocks came up when I went to the cs admin
office to get a livecd in order to fsck /. And they placated my fears
of having to grep [dd if=/dev/sda5 of=/mnt/backup/root.bin] to get the
important lines from /etc (my back ups are far too old) by stating
that ext2/3 has alt superblocks at regular intervals.JFS also has it
by implication, since ext2/3 is pretty much a subset of every
journaled fs in linux (counterexamples probably exist - I couldn't
care less).
--
001100 Andrey "m05hbear" Vul
010010
011110 andrey at moshbear dot net
100001 andrey dot vul at gmail
101101 416XXXXXXX
110011

Today's quote:
[ ] Obsolete code offends me.
[ ] Be aware of [ ] Murphy's, [ ] Muphry's Law.
[ ] Use [ ] Occam's, [ ] Hanlon's razor.
[ ] Greenspun's Tenth Rule.
[ ] Sturgeon's Law, [ ] Pareto principle.
[ ] RTFM, [ ] RTF[__]
[ ] [___]
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/