On Apr 08, 2007 22:24 -0500, Eric Sandeen wrote:
Samuel Thibault wrote:
Distribution installers usually try to probe OSes for building a suited
grub menu. Unfortunately, mounting an ext3 partition, even in read-only
mode, does perform some operations on the filesystem (log recovery).
This
On Sun, Apr 08, 2007 at 10:42:03PM -0500, Eric Sandeen wrote:
Samuel Thibault wrote:
Hm, so the root cause there seems that the installer found 2 legs of a
mirror and mounted them independently, recovering them independently...
But why did that cause problems?
Because that thrashed his
On Sun, 08 Apr 2007 22:24:50 CDT, Eric Sandeen said:
Can you elaborate? Under what circumstances is log replay going to harm
data? Do you mean that the installer mounts partitions, looking for
what OS is installed? How is that harmful?
Another usage case that really wants to avoid the log
On Mon, Apr 09, 2007 at 10:33:13AM +0800, coly wrote:
Theodore:
Thanks for your replying.
Can I understand this way:
* Though sizeof(struct ext4_inode) is 152, the real inode size on disk
still depends on mount options.
Not mount options, but how the filesystem is formatted. So
Jörn Engel writes:
Wouldn't that work be confined to fallocate()? If I understand Heiko
correctly, the alternative would slow s390 down for every syscall,
including more performance-critical ones.
The alternative that Jakub suggested wouldn't slow s390 down.
Paul.
-
To unsubscribe from this
Theodore:
Thanks for your explaining. I ignored this detail before, it is more
clear to me now.
Best regards.
Coly
在 2007-04-09一的 11:26 -0400，Theodore Tso写道：
On Mon, Apr 09, 2007 at 10:33:13AM +0800, coly wrote:
Theodore:
Thanks for your replying.
Can I understand this way:
*
Samuel Thibault wrote:
Hi,
Distribution installers usually try to probe OSes for building a suited
grub menu. Unfortunately, mounting an ext3 partition, even in read-only
mode, does perform some operations on the filesystem (log recovery).
This is not a good idea since it may silently garbage
On Apr 09, 2007, at 11:43:15, Phillip Susi wrote:
Samuel Thibault wrote:
Hi,
Distribution installers usually try to probe OSes for building a
suited grub menu. Unfortunately, mounting an ext3 partition, even
in read-only mode, does perform some operations on the filesystem
(log
On Apr 8 2007 22:24, Eric Sandeen wrote:
Samuel Thibault wrote:
Can you elaborate? Under what circumstances is log replay going to harm data?
Do you mean that the installer mounts partitions, looking for what OS is
installed? How is that harmful?
Hm, so the root cause there seems that
