From: Anders Saaby <as@cohaesio.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Bad things happening to journaled filesystem machines; Was: Oops in kjournald
Date: Tue, 11 Jan 2005 17:10:53 +0100 [thread overview]
Message-ID: <200501111710.53730.as@cohaesio.com> (raw)
Hi,
Well I just want to count my self in. - I have had quite a few of these
errors,
both on XFS and EXT3. I tried a lot of different 2.6.x kernels without
luck. (See other mails here on LKML from me and Jakob Oestergaard et al.)
It seems something is very broken in VFS(?) on 2.6 (atleast after 2.6.5,
which was the last kernel I didn't see this on, but had other errors that
forced me away from it).
Sadly it looks to me as if either noone cares (enough) about this, or noone
is capable of fixing it (myself included). :(
- 2.4.28 fixed it for me. - Just have to live with the poor performance.
Jeffrey E. Hundstad wrote:
> I've had 4 machines do the similiar things. It happens during backups
> or during updatedb. This has happened on 2.6.9, 2.6.10, 2.6.10-ac7, and
> 2.6.10-ac8. I've seen several similiar reports with journaled file
> systems. I use XFS exclusively; but have seen reports on XFS and EXT3.
> I would report something more useful but what I'm usually left with is
> XFS unmounted and nothing useful on the screen. This has been on Xeon,
> Pentium-3 and Athlon systems. ...wish I could report more but perhaps it
> will add /part/ of a data point.
>
--
Med venlig hilsen - Best regards - Meilleures salutations
Anders Saaby
Systems Engineer
------------------------------------------------
Cohaesio A/S - Maglebjergvej 5D - DK-2800 Lyngby
Phone: +45 45 880 888 - Fax: +45 45 880 777
Mail: as@cohaesio.com - http://www.cohaesio.com
------------------------------------------------
next reply other threads:[~2005-01-11 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 16:10 Anders Saaby [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-11 9:05 Oops in kjournald Roland Rosenfeld
2005-01-11 9:24 ` Bad things happening to journaled filesystem machines; Was: " Jeffrey E. Hundstad
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=200501111710.53730.as@cohaesio.com \
--to=as@cohaesio.com \
--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;
as well as URLs for NNTP newsgroup(s).