diff options
| author | Kalpak Shah <kalpak@clusterfs.com> | 2007-07-09 13:05:45 -0400 |
|---|---|---|
| committer | Theodore Ts'o <tytso@mit.edu> | 2007-07-10 07:28:35 -0400 |
| commit | 575307cc63d24766ff789262a5cea7b4faf2fa13 (patch) | |
| tree | 4d7b60b5f7a1a2656f239e8a06ad72dc9a0e3b59 /po/pl.po | |
| parent | 48b0ea41406970c21fadec2ef746968bdfb81e95 (diff) | |
| download | e2fsprogs-575307cc63d24766ff789262a5cea7b4faf2fa13.tar.gz | |
e2fsck: Fix salvage_directory when the last entry's rec_len is too big
Recently, one of our customers found this message in pass2 of e2fsck
while doing some regression testing:
"Entry '4, 0x695a, 0x81ff, 0x0040, 0x8320, 0xa192, 0x0021' in ??? (136554) has
rec_len of 14200, should be 26908."
Both the displayed rec_len and the "should be" value are bogus. The
reason is that salvage_directory sets a offset beyond blocksize
leading to bogus messages.
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Diffstat (limited to 'po/pl.po')
0 files changed, 0 insertions, 0 deletions