On Fri, Oct 05, 2012 at 11:12:39AM +0200, Richard Neuboeck wrote: > On 10/3/12 11:18 AM, Richard Neuboeck wrote: > > Hi, > > > > just in case someone stumbles over this thread in search for help. I > > found a solution. > > > > I upgraded the host machine from Ubuntu lucid to Ubuntu precise and > > expected the same mounting behavior like in the virtual machine running > > 'precise'. However on the host no error message showed up. > > > > Long story short after some test on the virtual machine configuration > > (libvirt, qemu/kvm) it turned out to be the 'caching=none' option. After > > changing this to <driver name='qemu' type='raw' cache='default'/> > > everything works. So, you converted it to use buffered IO. > And I forgot to mention that this 'bug' is still XFS dependent. It's not a bug if theproblem is a sector size mismatch in your configuration. You haven't provided any of the details that have been asked for to confirm this, so it would be appreciated if you could so we know in future.... > I have > the same setup RAID/LVM/virtio setup in use with ext4. Which works fine. > Either ext4 does something wrong so that it works or not I can not tell. > The end result is that ext4 works, xfs only with modification to the > virtual machine setup. ext4 only does filesystem block sized IOs, which by default will be 4k, and hence work just fine on a 4k sector size host filesystem. XFS does sector size IO in some cases, and that's where you appear to behaving problems. Assuming the problem is a sector size mismatch, then make your guest XFS filesystems use 4k sector size, and everything will be fine.... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
