public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Marko Weber|8000 <weber@zbfmail.de>
To: Xfs <xfs@oss.sgi.com>
Subject: Re: Cant mount xfs lvm. Experimental Features?
Date: Wed, 26 Aug 2015 01:10:41 +0200	[thread overview]
Message-ID: <e4d6436ce2242107ab96dd3be2669046@zbfmail.de> (raw)
In-Reply-To: <20150825230353.GK714@dastard>



Am 2015-08-26 01:03, schrieb Dave Chinner:
> On Wed, Aug 26, 2015 at 12:53:51AM +0200, Marko Weber|8000 wrote:
> [....]
>> 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.
>> 
>> 
>> this happens with the newly created logical volume.
>> 
>> the other 2 lvm partitions with xfs are fine.
>> 
>> any idea?
> 
> Clearly you have a kernel too old to read the on-disk format that
> mkfs.xfs has written - as I pointed out originally.
> 
> Would you please tell us what the versions of the kernels
> you are using, as well as the mkfs.xfs version?

Kernel vanilla-sources 3.14.51 (longterm support)
xfs-progs 3.2.4 (gentoo)
mkfs.xfs 3.2.4

AND HEY!  Eric, your hint worked:

backupserver ~ # mkfs.xfs -f -m crc=0,finobt=0 /dev/VolGroup01/vmstore
meta-data=/dev/VolGroup01/vmstore isize=256    agcount=4, 
agsize=19660800 blks
          =                       sectsz=4096  attr=2, projid32bit=1
          =                       crc=0        finobt=0
data     =                       bsize=4096   blocks=78643200, 
imaxpct=25
          =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0 ftype=0
log      =internal log           bsize=4096   blocks=38400, version=2
          =                       sectsz=4096  sunit=1 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
backupserver ~ # mount /dev/VolGroup01/vmstore /var/storage01/
backupserver ~ # df -h
Filesystem                      Size  Used Avail Use% Mounted on
/dev/root                        35G   21G   15G  60% /
devtmpfs                         10M     0   10M   0% /dev
tmpfs                           1.6G  464K  1.6G   1% /run
shm                             7.7G   72K  7.7G   1% /dev/shm
cgroup_root                      10M     0   10M   0% /sys/fs/cgroup
/dev/mapper/VolGroup01-backup   500G  396G  105G  80% 
/var/volgroup01/backup
/dev/mapper/VolGroup01-dumps    200G   89G  112G  45% /var/dumps
/dev/mapper/VolGroup01-vmstore  300G   33M  300G   1% /var/storage01



dave, so the latest lts kernel 3.14.51 does not support to mount lvm2 
partitions formatted with mkfs.xfs 3.2.4?


marko


> 
> Cheers,
> 
> Dave.

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

  reply	other threads:[~2015-08-25 23:10 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
2015-08-25 23:03         ` Dave Chinner
2015-08-25 23:10           ` Marko Weber|8000 [this message]
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=e4d6436ce2242107ab96dd3be2669046@zbfmail.de \
    --to=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