On Tue, Jun 29, 2004 at 11:19:56PM +0300, Markus Törnqvist wrote:
I'll just send this post now, I'll send a follow-up when I'm re-doing
fsck with some switches. This was just a basic fsck /dev/hda1, so maybe
no need to panic yet...
So I proceeded to --build-fs
FSCK: Node (481195), item (5),
On Wed, Jun 30, 2004 at 09:45:47AM +0300, Markus Törnqvist wrote:
So now I'll just compile the new auto-snapshot and see what happens...
It did not work.
http://mjt.nysv.org/reiser/Reiser4-2004.06.29/
Pictures once again courtesy of my trusty phone, so the quality truly
does suck.
So, err, I'm
On Wednesday 30 June 2004 13:03, Markus Trnqvist wrote:
On Wed, Jun 30, 2004 at 09:45:47AM +0300, Markus Trnqvist wrote:
So now I'll just compile the new auto-snapshot and see what happens...
It did not work.
http://mjt.nysv.org/reiser/Reiser4-2004.06.29/
Pictures once again courtesy of my
On Wed, Jun 30, 2004 at 01:24:34PM +0400, Vitaly Fertman wrote:
it prints all found corruptions. could you send them ?
The thing is, now that 2.6.7-mm4, latest auto-snapshot, failed,
I didn't get any errors with fsck... So it seems my filesystem
is all alright, at least for the time being.
btw,
On Wed, Jun 30, 2004 at 12:42:25PM +0300, Markus Törnqvist wrote:
I'm taking a debugfs.reiser4 -P /dev/hda1 now.
Then I will run additional stuff, but it still seems like the FS is ok
Yeah, I have the metadata dump now, and I will send it to you if you
feel you need it, but the additional
Hi!
* Tree Traverse Pass: scanning the reiser4 internal tree.
FSCK: Node (2013064): The last key [377f5f:4(FB):2e616339375f63:3a45d8:99] in 2 the
node is greater then the right delimiting key [2fa6e:4(FB):6c69626d70342e:1e88ad:1f7c].
FSCK: Node (469959), item (28), unit (0): Points to the
