From: Oleg Drokin <green@namesys.com>
To: Michael.James@csiro.au
Cc: reiserfs-list@namesys.com, jeffm@suse.com
Subject: Re: Un-long listable files (strace+Oops)
Date: Tue, 9 Sep 2003 18:47:42 +0400 [thread overview]
Message-ID: <20030909144742.GA3177@namesys.com> (raw)
In-Reply-To: <200309091512.11914.Michael.James@csiro.au>
Hello!
On Tue, Sep 09, 2003 at 03:12:11PM +1000, Michael.James@csiro.au wrote:
> I'm getting un-long listable files cropping up occasionally.
> (on a Suse8.2 system, Reiserfs 3.6)
Yes, I remember that case. (it was related to xattrs last time)
> Please get in touch directly if you are interested,
> particularily if there is some other test I could perform.
> Generally I find having these files around an irritating form of bitrot,
> so I get rid of them, which can hinder investigations
> as I can't create them repeatably.
Hm, but do you get an oops each time before you see such files?
> Here's an strace of what happens when I "ls -l it.
> suse:/home/pi/jam176/tmp # cat strace.ls-l
[...]
> lstat64("KNOPPIX_V3.2-2003-07-26-EN.iso", {st_mode=S_IFREG|0644, st_size=290107392, ...}) = 0
> getxattr("KNOPPIX_V3.2-2003-07-26-EN.iso", "system.posix_acl_access"s
Ok, and in hung at xattrs stuff again.
May be Jeff will be interested in metadata snapshot of corrupted fs.
> And there it hangs, waiting for heat-death-of-universe.
> Sep 3 12:39:13 suse kernel: Unable to handle kernel paging request at virtual address 00001d08
> Sep 3 12:39:13 suse kernel: EIP: 0010:[__find_lock_page_helper+23/96] Tainted: PF
Hm, you have binary modules loaded. What are those?
Can you reproduce without those modules ever loaded?
> Sep 3 12:39:15 suse kernel: Call Trace: [generic_file_write_nolock+705/2000] [generic_file_write+56/80] [reiserfs:__insmod_reiserfs_S.text_L165788+51778/139792] [sys_write+120/256] [system_call+51/64]
Otherwise the oops does not even looks like reiserfs related, just some in-memory corruption.
Bye,
Oleg
next prev parent reply other threads:[~2003-09-09 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 4:31 un-long listable files Michael.James
2003-08-06 17:03 ` Oleg Drokin
2003-08-06 18:06 ` Jeff Mahoney
[not found] ` <200308070823.40130.Michael.James@csiro.au>
[not found] ` <3F3188C5.7050606@suse.com>
2003-09-09 5:12 ` Un-long listable files (strace+Oops) Michael.James
2003-09-09 14:47 ` Oleg Drokin [this message]
2003-09-09 15:00 ` Jeff Mahoney
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=20030909144742.GA3177@namesys.com \
--to=green@namesys.com \
--cc=Michael.James@csiro.au \
--cc=jeffm@suse.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.