From: Marko Weber|8000 <weber@zbfmail.de>
To: Xfs <xfs@oss.sgi.com>
Subject: Re: Cant mount xfs lvm. Experimental Features?
Date: Tue, 25 Aug 2015 18:51:05 +0200 [thread overview]
Message-ID: <5ab00519660fd5ed1b3d347658dba1f2@zbfmail.de> (raw)
In-Reply-To: <20150825115412.GI714@dastard>
dave,
Am 2015-08-25 13:54, schrieb Dave Chinner:
> On Tue, Aug 25, 2015 at 10:25:16AM +0200, Marko Weber|8000 wrote:
>>
>> Hello List, Hello Dave...
>>
>>
>> i try to mount on my backup server an Lvm Partition and get errors
>> in stdout and log:
>>
>> /var/log/messages:
>>
>> Aug 25 10:20:31 backupserver kernel: XFS (dm-2): Version 5
>> superblock detected. This kernel has EXPERIMENTAL support enabled!
>> Aug 25 10:20:31 backupserver kernel: Use of these features in this
>> kernel is at your own risk!
>> Aug 25 10:20:31 backupserver kernel: XFS (dm-2): Superblock has
>> unknown read-only compatible features (0x1) enabled.
>> Aug 25 10:20:31 backupserver kernel: XFS (dm-2): Attempted to mount
>> read-only compatible filesystem read-write.
>> Aug 25 10:20:31 backupserver kernel: Filesystem can only be safely
>> mounted read only.
>> Aug 25 10:20:31 backupserver kernel: XFS (dm-2): SB validate failed
>> with error 22.
>
> You need to run the same version kernel on both servers. The primary
> has a more recent kernel and feature set than your older backup
> server is running.
>
> Cheers,
>
> Dave.
you was right.
There was new kernel built. /usr/src/linux pointed to new kernel source.
But machine was not rebooted. So kernel version before kernel built was
loaded.
I rebooted machine.
i renoved logical volume
i created logical volume
i tried to mount it and get:
Aug 25 18:43:15 backupserver kernel: md4: unknown partition table
Aug 25 18:43:15 backupserver syslog-ng[1417]: Internal error,
alarm_set() called while an alarm is still active;
Aug 25 18:43:56 backupserver kernel: md4: unknown partition table
Aug 25 18:44:01 backupserver kernel: XFS (dm-2): Invalid superblock
magic number
pvdisplay shows:
# pvdisplay
--- Physical volume ---
PV Name /dev/md4
VG Name VolGroup01
PV Size 2.69 TiB / not usable 1.25 MiB
so what is XFS missing?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-08-25 16:51 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 [this message]
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
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=5ab00519660fd5ed1b3d347658dba1f2@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