Re: Fix(es) for ext2 fsync bug

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

 



On Tue, 2007-02-20 at 21:39 +0000, Valerie Henson wrote:
> On Tue, Feb 20, 2007 at 01:30:25PM -0800, Junfeng Yang wrote:
> > On 2/20/07, Valerie Henson <val_henson@xxxxxxxxxxxxxxx> wrote:
> > >
> > >Google. (GoogleFS runs on top of ext2.)
> >
> > It's surprising to know that... I guess they reply on GoogleFS's own
> > replication and checksumming for consistency.
> 
> Yep, they just want a local file system with ultrafast on-line
> performance.  They don't care about recovery time particularly because
> of the GoogleFS replication (although I heard rumors they have some
> fast fsck scheme, maybe resembling the dirty bit stuff I did last
> year).

I wonder if they would consider this a important bug?  I know nothing
about GoogleFS, but I would guess that they have more sophisticated
recovery than relying on an fsync shortly before a crash to ensure data
integrity.

Shaggy
-- 
David Kleikamp
IBM Linux Technology Center

-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux