Re: [ext3] Changes to block device after an ext3 mount point has been remounted readonly

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

 



On 2010-02-22, at 16:05, Jan Kara wrote:
Hmm, and apparently there is some subtlety in the loopback device code because even when I use sync(1), the first and second images sometimes differ (although it's much rarer). But I see a commit block of the transaction already in the first image (the commit block is written last) but the contents of the transaction is present only in the second image.


It has never been safe to run ext3 on top of a loop device, because the loop device does not preserve ordering, and I'm not sure whether it properly passes barriers either.

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

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

[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux