[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re[2]: bdflush (was: corrupt inode)

To: linux-xfs@oss.sgi.com
Subject: Re[2]: bdflush (was: corrupt inode)
From: Keith Matthews <keith_m@sweeney.demon.co.uk>
Date: Thu, 9 Aug 2001 18:25:04 +0100 (BST)
In-reply-to: <4.3.2.7.2.20010809163227.0333b8f8@pop.xs4all.nl>
References: <3B7296F9.E1FAB9CA@fnal.gov>,<4.3.2.7.2.20010809163227.0333b8f8@pop.xs4all.nl>
Sender: owner-linux-xfs@oss.sgi.com

On Thu, 09 Aug 2001 18:43:34 +0200 Seth Mos <Seth Mos <knuffie@xs4all.nl>> wrote:


> The journaling fs is not to blame, it does it's work correctly. The 
> application needs to have some form of modern day filesystems. Does anybody 
> have a ReiserFS or JFS filesystem to test this with?

I would say that JFS, ReiserFS and ext3 in metada-only mode will give
substantially the same result. Only ext3 in full journalling mode will differ.


--
Keith Matthews 			Spam trap - my real account at this 
							node is keith_m
Frequentous Consultants  - Linux Services, 
		Oracle development & database administration

References:
- Re: bdflush (was: corrupt inode)
  - From: Seth Mos <knuffie@xs4all.nl>

Prev by Date: Re: unable to open initial console
Next by Date: Re: 3ware driver and XFS kernel from SGI (YAMTR)
Previous by thread: Re: bdflush (was: corrupt inode)
Next by thread: OT: WMware beta
Index(es):
- Date
- Thread