From: Dave Chinner <david@fromorbit.com>
To: Richard Neuboeck <hawk@tbi.univie.ac.at>
Cc: xfs@oss.sgi.com
Subject: Re: xfs mount fails 'can't read superblock'
Date: Sat, 6 Oct 2012 10:17:57 +1000 [thread overview]
Message-ID: <20121006001757.GE23644@dastard> (raw)
In-Reply-To: <506EA487.8050903@tbi.univie.ac.at>
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@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-10-06 0:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 8:49 xfs mount fails 'can't read superblock' Richard Neuboeck
2012-09-18 20:55 ` Dave Chinner
2012-09-22 9:33 ` Richard Neuboeck
2012-10-03 9:18 ` Richard Neuboeck
2012-10-05 9:12 ` Richard Neuboeck
2012-10-06 0:17 ` Dave Chinner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121006001757.GE23644@dastard \
--to=david@fromorbit.com \
--cc=hawk@tbi.univie.ac.at \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox