From: Paul Pluzhnikov <ppluzhnikov@gmail.com>
To: reiserfs-list@namesys.com
Subject: Re: "reiserfsck --fix-fixable" says corrected; but doesn't
Date: Sat, 15 Apr 2006 22:25:22 -0700 [thread overview]
Message-ID: <4441D542.8020000@gmail.com> (raw)
In-Reply-To: <4441BEA6.3020103@gmail.com>
Paul Pluzhnikov wrote:
> Running with '--fix-fixable' finds the same errors, and says
> that it fixed them; but running again finds the same problem again.
Additional clues: the FS (being version 3.5) does not support files over
2GB.
All 3 files with the problem are a result of a (recent) program
attempting to create a file that is larger than 2GB.
So, AFAICT:
- attempts to write large files on a 3.5 formatted FS (mounted without
"-o conv") result in an error returned to a client program, and in
filesystem corruption (actual size (as computed by reiserfsck) exceeds
the limit) -- kernel BUG!
- attempts to fix such corruption with the latest reiserfsprogs
don't actually fix it -- reiserfsprogs BUG!
I have removed the 3 offending files (by moving them into lost+found first),
and can do "ls" again :)
However this resulted in additional corruption which wasn't there before :(
bad_leaf: block 18522164, items 12 and 13: The wrong order of items:
[134215 570889 0x1 DRCT (2)], [134215 570890 0x1 IND (1)] ...
Fatal corruptions were found, Semantic pass skipped
1 found corruptions can be fixed only when running with --rebuild-tree
I'll probably just back up the data and reformat the FS.
Cheers,
next prev parent reply other threads:[~2006-04-16 5:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-16 3:48 "reiserfsck --fix-fixable" says corrected; but doesn't Paul Pluzhnikov
2006-04-16 5:25 ` Paul Pluzhnikov [this message]
2006-04-17 4:13 ` Neal Murphy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4441D542.8020000@gmail.com \
--to=ppluzhnikov@gmail.com \
--cc=reiserfs-list@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.