From: Jan Kara <jack@suse.cz>
To: "Vladimír Třebický" <druid@mail.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Filesystem strangeness (ext3)
Date: Mon, 5 Apr 2004 18:32:28 +0200 [thread overview]
Message-ID: <20040405163228.GF22380@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <1014938126.20040405120812@xhost.cz>
Hi,
> yesterday I discovered a bunch of corrupted files. When I try to stat()
> it, I get "Value too large for defined data type" or "Input/output
> error" when it is a symlink to those files. These were normal files
> (some readmes etc.) not accessed by any daemons or any applications at
> all. Midnight marks them with "?" at beginning and shows something
> about 3GB size. When I try to unlink() them, I get "Operation not
> permitted" even though I'm root. Kernel log shows these two kinds of
> errors:
>
> Apr 5 11:33:47 master kernel: init_special_inode: bogus imode (113315)
>
> and
>
> Apr 5 11:33:49 master kernel: attempt to access beyond end of device
> Apr 5 11:33:49 master kernel: 09:01: rw=0, want=587173332, limit=38539776
It seems like something trashed part of your disk...
> When I try to e2fsck -nf (I tried only ro test on mounted partition) I
> get some of these:
>
> Illegal block #10 (2236192626) in inode 523442. IGNORED.
I suggest at least remounting the partition ro and then run the ro-test.
> and:
>
> Error while iterating over blocks in inode 523442: Illegal triply indirect block found
> Segmentation fault
Bug in e2fsck - you probably want to download latest version of e2fsck. If
there is still this bug report to e2fsck authors.
> It confuses me a little bit and I don't know wheter I should try to do
> rw e2fsck on unmounted partition, especially when e2fsck segfaults. My
You should definitely backup the partition before you run fsck on it.
> system:
>
> Linux master 2.4.22 #1 Sat Sep 20 14:26:11 CEST 2003 i686 unknown
> e2fsck 1.27 (8-Mar-2002)
> Using EXT2FS Library version 1.27, 8-Mar-2002
> The device is /dev/md1:
>
> [dev 9, 1] /dev/md1 889E3491.06B38BDD.B6F3803F.BCE40C0E online
> [dev 3, 7] /dev/hda7 889E3491.06B38BDD.B6F3803F.BCE40C0E good
> [dev 3, 71] /dev/hdb7 889E3491.06B38BDD.B6F3803F.BCE40C0E good
>
> smartctl shows no errors on those physical disks.
Honza
--
Jan Kara <jack@suse.cz>
SuSE CR Labs
prev parent reply other threads:[~2004-04-05 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 10:08 Vladimír Třebický
2004-04-05 15:17 ` Andreas Dilger
2004-04-05 16:32 ` Jan Kara [this message]
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=20040405163228.GF22380@atrey.karlin.mff.cuni.cz \
--to=jack@suse.cz \
--cc=druid@mail.cz \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®