From: Alex Riesen <Alexander.Riesen@synopsys.com>
To: Tim Alexeevsky <realtim@mail.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: File accessing.
Date: Tue, 9 Jul 2002 13:47:49 +0200 [thread overview]
Message-ID: <20020709114749.GB32293@riesen-pc.gr05.synopsys.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0207091326550.390-100000@zhuchka>
On Tue, Jul 09, 2002 at 01:47:41PM +0400, Tim Alexeevsky wrote:
> Hello,
>
> Today Alex Riesen wrote:
>
> AR>On Sun, Jul 07, 2002 at 02:40:26AM +0400, Tim Alexeevsky wrote:
> AR>...
> AR>> Using strace I tracked this problem down to requesting
> AR>> open("jffs2/gc.c", O_READONLY|O_LARGEFILE)
> AR>> Now
> AR>> ls jffs2
> AR>> also gives me a kernel panic. It's on reiserfs.
> AR>>
> AR>
> AR>i'd suggest you start your next day/night with reiserfsck --fix-fixable.
> Sure :)
>
> AR>And you'll have to upgrade your reiserfsprogs up to 3.x.1b.
> Ok.
>
> But if this is the reason for this subproblem, there are some others
> and they all seem to appear simultaneously. They all are the problems with
> accessing files. And as long as I got the first problem I will have a
> lots of them on different filesystems until I reboot the system (AFAIK).
> Maybe the reason is some damage in global filesystem handling. (Is that
> VFS?)
that's not the reason 8-) That are consequences.
Maybe upgrade the kernel as well? 2.4.19-rc1 seems to be quiet stable
for me and there was some changes to reiserfs since 2.4.17.
next prev parent reply other threads:[~2002-07-09 11:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-06 22:40 Tim Alexeevsky
2002-07-09 6:48 ` Alex Riesen
2002-07-09 9:47 ` Tim Alexeevsky
2002-07-09 11:47 ` Alex Riesen [this message]
2002-07-09 13:09 ` Tim Alexeevsky
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=20020709114749.GB32293@riesen-pc.gr05.synopsys.com \
--to=alexander.riesen@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=realtim@mail.ru \
/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®