On Jan 05, 2002 08:49 +1000, Adrian Head wrote: > Well this seems consistant with what I'm seeing: > 2.4.17-xfs > While source volume mounted: > + lvm-1.0.1 upgrade > + VFS-lock > (In that order) > * Can create ext3 snapshot? | yes > * Can mount a ext3 snapshot? | yes > * Can create resierfs snapshot? | yes > * Can mount a resierfs snapshot? | yes > * Can create xfs snapshot? | Oops > btp 1234 (lvcreate) > journal_start > ext3_dirty_inode > __mark_inode_dirty > update_atime > do_generic_file_read > generic_file_read > sys_read > system_call Can you repeat this test, but skip the ext3 snapshot creation part of it entirely (i.e. create a reiserfs snapshot and an XFS snapshot, without changing the kernel)? I'm wondering if XFS is getting an old inode that ext3 was using, but either ext3 or XFS is not clearing it, so that is why it is calling into ext3. Also, are you using ext3 on other filesystems in this computer? Cheers, Andreas -- Andreas Dilger http://sourceforge.net/projects/ext2resize/ http://www-mddsp.enel.ucalgary.ca/People/adilger/
