public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: weber@zbfmail.de
Cc: Xfs <xfs@oss.sgi.com>
Subject: Re: Cant mount xfs lvm. Experimental Features?
Date: Wed, 26 Aug 2015 09:16:36 +1000	[thread overview]
Message-ID: <20150825231636.GL714@dastard> (raw)
In-Reply-To: <5576eb52ccfa8182ca150a99436be93c@zbfmail.de>

On Wed, Aug 26, 2015 at 01:02:58AM +0200, Marko Weber|8000 wrote:
> Am 2015-08-26 00:58, schrieb Eric Sandeen:
> >On 8/25/15 5:53 PM, Marko Weber|8000 wrote:
> >
> >>eric,
> >>i rebootet the machine and created a new logical volume.
> >>i formatted the lv with mkfs.xfs
> >>i tried to mount it on the new kernel:
> >>
> >>Aug 26 00:47:17 backupserver kernel: XFS (dm-2): Version 5
> >>superblock detected. This kernel has EXPERIMENTAL support
> >>enabled!
> >>Aug 26 00:47:17 backupserver kernel: Use of these features in
> >>this kernel is at your own risk!
> >>Aug 26 00:47:17 backupserver kernel: XFS (dm-2): Superblock has
> >>unknown read-only compatible features (0x1) enabled.
> >>Aug 26 00:47:17 backupserver kernel: XFS (dm-2): Attempted to
> >>mount read-only compatible filesystem read-write.
> >>Aug 26 00:47:17 backupserver kernel: Filesystem can only be
> >>safely mounted read only.
> >>Aug 26 00:47:17 backupserver kernel: XFS (dm-2): SB validate
> >>failed with error 22.
> >l
> >http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
> >...
> >
> >>this happens with the newly created logical volume.
> >>
> >>the other 2 lvm partitions with xfs are fine.
> >>
> >>any idea?
> >
> >Without any actual information (i.e. kernel versions or userspace
> >version),
> >I'll have to assume that you have recent xfsprogs which sets some
> >features by
> >default which older kernels cannot understand.
> 
> ok, what info do you need?
> 
> on gentoo-linux:
> 
> xfsprogs: v 3.2.4 (Useflag, nls readline)
> kernel:   3.14.51

Kernel is too old for finobt=1, and really too old for CRCs to be
enabled (not fully supported until 3.16).

So, either:

> >mkfs.xfs with -m crc=0,finobt=0 to turn off these features if you have
> >an older kernel which
> >doesn't understand them.

or upgrade your kernel.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2015-08-25 23:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25  8:25 Cant mount xfs lvm. Experimental Features? Marko Weber|8000
2015-08-25 11:54 ` Dave Chinner
2015-08-25 16:51   ` Marko Weber|8000
2015-08-25 18:18     ` Eric Sandeen
2015-08-25 19:26       ` Marko Weber|8000
2015-08-25 20:04         ` Eric Sandeen
2015-08-25 22:53       ` Marko Weber|8000
2015-08-25 22:58         ` Eric Sandeen
2015-08-25 23:02           ` Marko Weber|8000
2015-08-25 23:16             ` Dave Chinner [this message]
2015-08-25 23:03         ` Dave Chinner
2015-08-25 23:10           ` Marko Weber|8000
2015-08-25 23:33             ` Dave Chinner
2015-08-26 10:30               ` Marko Weber|8000

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=20150825231636.GL714@dastard \
    --to=david@fromorbit.com \
    --cc=weber@zbfmail.de \
    --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