On Tue 29-11-11 07:54:28, Mikulas Patocka wrote: > > > This is technically impossible to achieve on ext2, fat or other > > > non-transactional filesystems. These filesystems have no locks around code > > > paths that set data or inodes dirty. And you still need working sync for > > > ext2. So the best thing to do in sync is to wait until the filesystem is > > > unfrozen. > > Then suspend is effectively unsupported on the filesystem and should > > return EOPNOTSUPP? At least that's what I'd expect... > > LVM uses suspend every time it changes layout of the logical volume. For > example when it converts to/from mirrored format, extends/shrinks the > volume, moves the volume to a different disk, takes a snapshots, merges a > snapshot back, on mirror or multipath failover. > > For most of these actions (except taking a snapshot) it is irrelevant if > there are dirty data in the filesystem cache or not while it is suspended. Hmm, then why do these operations suspend the filesystem if they apparently don't need it? Sorry for my ignorance, I never seriously worked with LVM code... Honza -- Jan Kara <jack@xxxxxxx> SUSE Labs, CR -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
