Skip to contentSkip to conversation

Bad things happening to journaled filesystem machines; Was: Oops in kjournald

DISCUSSION Anders Saaby 1 participant 1 message Jan 11, 2005

lore
Share & tools
lore
#0 lore 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.

Quoted 9 lines · Jeffrey E. Hundstad

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.

Signature · 9 lines
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: [email protected] - http://www.cohaesio.com
------------------------------------------------