[Bug 557745] New: Write on a XFS formated logical volume after a snapshot (lvm2) on a DomU paravitualized

older
[Bug 390924] opensuse-updater-kde...

bugzilla_noreply＠novell.com

23 Nov 2009 23 Nov '09

13:55

http://bugzilla.novell.com/show_bug.cgi?id=557745 http://bugzilla.novell.com/show_bug.cgi?id=557745#c0 Summary: Write on a XFS formated logical volume after a snapshot (lvm2) on a DomU paravitualized Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: Xen AssignedTo: jdouglas@novell.com ReportedBy: martineau.antony@free.fr QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.0.15) Gecko/2009101601 Firefox/3.0.15 (.NET CLR 3.5.30729) I reproduct this bug on DomU paravirtualized opensuse11.1 and Ubuntu server 9.10 In a domU when i mount a logical volume formated in XFS no problem. But when i do a snapshot of this logical volume the disk becomes innacessible. 1 - I start my domU whith 2 disks (/dev/vg0/lv0,(hda) and /dev/vg0/lv1(hdc) i format hdc whith xfs and i mount it on /media no problem : XFS mounting filesystem hdc Ending clean XFS mount for filesystem: hdc (writes and reads on this disk is ok) 2- I do a snapshot on Dom0 about /dev/vg0/lv1 On domU i have immediatly this error.. blkfront: hdc: write barrier op failed blkfront: hdc: barriers disabled end_request: I/O error, dev hdc, sector 2097186 end_request: I/O error, dev hdc, sector 2097186 Filesystem "hdc": xlog_iodone: Barriers are no longer supported by device. Disabling barriers the disk become inaccessible... the same thing if i try on hda... the system crash because it is the system disk. The problem is not present whith ext3 or ext4 on disk... The problem seems to be beetween XFS Barriers on LVM2 and blkfront... blkfront is not capable to use xfs barriers... Reproducible: Always Steps to Reproduce: 1.Install Dom0 opensuse11.1 up to date 2.Install DomU opensuse11.1 paravirtualized on logical volume for example /dev/vg0/lv0 (hda) and /dev/vg0/lv1 (hdc) 3.In DomU format hdc disk whith XFS and mount it 4.In Dom0 do a snapshot of hdc /dev/vg0/lv1 (not hda because freeze the system) 5.In DomU looks the dmesg ( error blkfront: hdc: write barrier op failed must be appeared) Actual Results: the disks whith snapshot is inaccessible and disabling xfs barriers -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Show replies by date

bugzilla_noreply＠novell.com

23 Nov 23 Nov

17:07

New subject: [Bug 557745] Write on a XFS formated logical volume after a snapshot (lvm2) on a DomU paravitualized

http://bugzilla.novell.com/show_bug.cgi?id=557745 http://bugzilla.novell.com/show_bug.cgi?id=557745#c1 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jfehlig@novell.com, | |wkong@novell.com --- Comment #1 from James Fehlig 2009-11-23 17:07:06 UTC --- Ignoring the bug you are seeing with XFS, I wonder if the steps you perform are valid. If domU is running and doing IO to the disk, would the snapshot be consistent? Could you subsequently mount that snapshot without any corruption issues? I suspect this is no different than a native scenario where a service is writing to a LVM volume and snapshots are taken on the volume while services is active. One thing you could do as a possible workaround is save the vm before snapshot and then restore. E.g. your step 4 above would be: 4a. Save domU (xm save domU-name /path) 4b. In Dom0 do a snapshot of hdc /dev/vg0/lv1 4c. Restore domU (xm restore /path) This should also allow snapshotting of hda device. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

17:32

New subject: [Bug 557745] Write on a XFS formated logical volume after a snapshot (lvm2) on a DomU paravitualized

http://bugzilla.novell.com/show_bug.cgi?id=557745 http://bugzilla.novell.com/show_bug.cgi?id=557745#c2 --- Comment #2 from MARTINEAU Antony 2009-11-23 17:32:09 UTC --- Thanks for your answer. But it is not the question. the problem is not having a consistent snapshot for backup. The problem is that i can not write on a XFS/logical volume on a domU when there is a snapshot... Normally Doing snapshot don't deny the access of the disk, When a block is modified, the original must be copied on cow table... it is the copy on write. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

18:02

New subject: [Bug 557745] Write on a XFS formated logical volume after a snapshot (lvm2) on a DomU paravitualized

http://bugzilla.novell.com/show_bug.cgi?id=557745 http://bugzilla.novell.com/show_bug.cgi?id=557745#c3 --- Comment #3 from James Fehlig 2009-11-23 18:02:30 UTC --- I understand your original description, but still suggest "save -> lvcreate -s -> restore" as a _workaround_. We need XFS maintainer to investigate and comment. Kong, were you involved in a similar bug recently? Can you take a look and reassign as needed? Thanks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

24 Nov 24 Nov

17:13

New subject: [Bug 557745] Write on a XFS formated logical volume after a snapshot (lvm2) on a DomU paravitualized

http://bugzilla.novell.com/show_bug.cgi?id=557745 http://bugzilla.novell.com/show_bug.cgi?id=557745#c Jason Douglas changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jdouglas@novell.com AssignedTo|jdouglas@novell.com |wkong@novell.com -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

7 Dec 7 Dec

09:26

New subject: [Bug 557745] Write on a XFS formated logical volume after a snapshot (lvm2) on a DomU paravitualized

http://bugzilla.novell.com/show_bug.cgi?id=557745 http://bugzilla.novell.com/show_bug.cgi?id=557745#c4 --- Comment #4 from wei kong 2009-12-07 09:26:48 UTC --- So sorry, I miss this bug. It seems your host is not SLES? LVM2 on sles11 doesn't support WRITE BARRIER on LV which combined by more than one physical device. So you host(Ubuntu server) seems not support either. Currently on OpenSUSE11.2/SLES11.1-alpha3 LVM support WRITE BARRIER. I test on SLES11.1-alpha3, works. Workaround way, maybe late, sorry. Mount your xfs in guest with nobarrier option -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

09:37

New subject: [Bug 557745] Write on a XFS formated logical volume after a snapshot (lvm2) on a DomU paravitualized

http://bugzilla.novell.com/show_bug.cgi?id=557745 http://bugzilla.novell.com/show_bug.cgi?id=557745#c6 --- Comment #6 from MARTINEAU Antony 2009-12-07 09:37:47 UTC --- I have ever try to mount xfs whith no barrier option on DomU. But the problem was the same ... the problem is xfs on the system Disk because it can freeze the system... Whith DomU Paravirtualized, no problem with ext4 file system in domU -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

09:40

New subject: [Bug 557745] Write on a XFS formated logical volume after a snapshot (lvm2) on a DomU paravitualized

http://bugzilla.novell.com/show_bug.cgi?id=557745 http://bugzilla.novell.com/show_bug.cgi?id=557745#c7 --- Comment #7 from MARTINEAU Antony 2009-12-07 09:40:42 UTC --- My LV is not combined by more than one physical devices. My LV are on phisical volume on only one physical Disk -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

09:56

New subject: [Bug 557745] Write on a XFS formated logical volume after a snapshot (lvm2) on a DomU paravitualized

http://bugzilla.novell.com/show_bug.cgi?id=557745 http://bugzilla.novell.com/show_bug.cgi?id=557745#c8 --- Comment #8 from wei kong 2009-12-07 09:56:23 UTC ---

...

I have ever try to mount xfs whith no barrier option on DomU. But the problem was the same ...

? so pls check /proc/mounts and dmesg, it's real nobarrier. I test xfs with nobarrier on SLES11 guest, works. If it still happen, can I access your test machine to do a debug. thanks

...

the problem is xfs on the system Disk because it can freeze the system...

Whith DomU Paravirtualized, no problem with ext4 file system in domU

I didn't test ext4 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10:01

New subject: [Bug 557745] Write on a XFS formated logical volume after a snapshot (lvm2) on a DomU paravitualized

http://bugzilla.novell.com/show_bug.cgi?id=557745 http://bugzilla.novell.com/show_bug.cgi?id=557745#c9 --- Comment #9 from MARTINEAU Antony 2009-12-07 10:01:52 UTC --- Yes of course just the time to make a test platform. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10:26

New subject: [Bug 557745] Write on a XFS formated logical volume after a snapshot (lvm2) on a DomU paravitualized

http://bugzilla.novell.com/show_bug.cgi?id=557745 http://bugzilla.novell.com/show_bug.cgi?id=557745#c11 --- Comment #11 from MARTINEAU Antony 2009-12-07 10:25:52 UTC --- And whith barrier on XFS have you got the problem? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

11:07

New subject: [Bug 557745] Write on a XFS formated logical volume after a snapshot (lvm2) on a DomU paravitualized

http://bugzilla.novell.com/show_bug.cgi?id=557745 http://bugzilla.novell.com/show_bug.cgi?id=557745#c12 --- Comment #12 from MARTINEAU Antony 2009-12-07 11:07:01 UTC --- suse:~ # cat /proc/mounts rootfs / rootfs rw 0 0 udev /dev tmpfs rw,mode=755 0 0 /dev/hda3 / xfs rw,attr2,nobarrier,noquota 0 0 /proc /proc proc rw 0 0 sysfs /sys sysfs rw 0 0 debugfs /sys/kernel/debug debugfs rw 0 0 devpts /dev/pts devpts rw,gid=5,mode=620 0 0 /dev/hda1 /boot xfs rw,attr2,nobarrier,noquota 0 0 fusectl /sys/fs/fuse/connections fusectl rw 0 0 securityfs /sys/kernel/security securityfs rw 0 0 none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0 ####CONFIG FILE##### ######VM PARAM#### name="susepara" ostype="linux" memory=1024 vcpus=2 cpu_weight=256 cpu_cap=0 hap=1 apic=1 acpi=1 pae=1 stdvga=0 usb=1 usbdevice="tablet" serial="pty" timer_mode=1 localtime=1 extid=0 on_crash="restart" on_reboot="restart" on_poweroff="destroy" ######HVM######### #builder="hvm" #device_model="/usr/lib64/xen/bin/qemu-dm" #kernel="/usr/lib/xen/boot/hvmloader" ######PVM######### builder="linux" bootloader = '/usr/lib/xen/boot/domUloader.py' bootargs = '--entry=hda1:vmlinuz-xen,initrd-xen' root="/dev/hda3" ######DEV######### vfb=[ 'type=vnc,vncunused=1', ] disk=[ 'phy:/dev/vg0/lv0,hda,w', 'phy:/dev/vg0/lv1,hdc,w' , ] vif=[ 'type=netfront,mac=00:16:3a:11:11:00', ] boot="c" ~ I can't reproduce the problem whith nobarrier option But When disks on domU are mounted whith barrier the problem is easy to reproduce Dom0 on opensuse11.1 x86_64, DomU on opensuse11.1 x86_64 para (/dev/vg0/lv0 system disk) when i do a snap about /dev/vg0/lv0, there is no one commande works.. If i mount /dev/hdc1 ( data disk on domU) the log is Dec 7 12:02:08 suse kernel: XFS: bad magic number Dec 7 12:02:08 suse kernel: XFS: SB validate failed Dec 7 12:02:15 suse kernel: XFS: bad magic number Dec 7 12:02:15 suse kernel: XFS: SB validate failed Dec 7 12:02:30 suse kernel: XFS mounting filesystem hdc1 Dec 7 12:02:30 suse kernel: Ending clean XFS mount for filesystem: hdc1 if i do a snap of /dev/vg0/lv1 ( correspond to /dev/hdc) linux:/stock # lvcreate -s -L2G -nlv1snap /dev/vg0/lv1 Logical volume "lv1snap" created On the domU the log is: Dec 7 12:04:52 suse kernel: blkfront: hdc: write barrier op failed Dec 7 12:04:52 suse kernel: blkfront: hdc: barriers disabled Dec 7 12:04:52 suse kernel: end_request: I/O error, dev hdc, sector 16771937 Dec 7 12:04:52 suse kernel: end_request: I/O error, dev hdc, sector 16771937 Dec 7 12:04:52 suse kernel: I/O error in filesystem ("hdc1") meta-data dev hdc1 block 0xffeb22 ("xlog_iodone") error 5 buf count 1536 Dec 7 12:04:52 suse kernel: xfs_force_shutdown(hdc1,0x2) called from line 1056 of file fs/xfs/xfs_log.c. Return address = 0xffffffffa00d1929 Dec 7 12:04:52 suse kernel: Filesystem "hdc1": Log I/O Error Detected. Shutting down filesystem: hdc1 Dec 7 12:04:52 suse kernel: Please umount the filesystem, and rectify the problem(s) Dec 7 12:04:54 suse kernel: Filesystem "hdc1": xfs_log_force: error 5 returned. You can test on this platform: (ssh) Dom0 ip=88.191.84.35 password=testpass domU (susepara) ip=192.168.1.1 password=testpass if you crash definitivly the domU you can restore it whith the template on /stock lzop -dc /stock/opensuse11.1-uptodate-para-password-testpass.lzo | dd of=/dev/vg0/lv0 bs=1M I am testing on ubuntu 9.10 whith nobarrier.. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

8 Dec 8 Dec

03:33

New subject: [Bug 557745] Write on a XFS formated logical volume after a snapshot (lvm2) on a DomU paravitualized

http://bugzilla.novell.com/show_bug.cgi?id=557745 http://bugzilla.novell.com/show_bug.cgi?id=557745#c13 --- Comment #13 from wei kong 2009-12-08 03:32:53 UTC ---

...

And whith barrier on XFS have you got the problem? Yes.

...

I can't reproduce the problem whith nobarrier option Good news.

...

But When disks on domU are mounted whith barrier the problem is easy to reproduce Dom0 on opensuse11.1 x86_64, DomU on opensuse11.1 x86_64 para (/dev/vg0/lv0 system disk) Yes, on opensuse11.1(Dom0), LVM2 doesn't support Write Barrier fully.

...

when i do a snap about /dev/vg0/lv0, there is no one commande works.. I just tested on your machine, with nobarrier works, see testsn2 is base on lv0.

...

Dec 7 12:02:08 suse kernel: XFS: bad magic number Dec 7 12:02:08 suse kernel: XFS: SB validate failed Your XFS fs super block destroyed, it recovered itself.

I have checked on your machine, with nobarrier works. this option has no performance problem. So you can use it. If you don't like this workaround way, try opensuse11.2/SLES11.1 as Dom0, they don't need this option. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

09:17

New subject: [Bug 557745] Write on a XFS formated logical volume after a snapshot (lvm2) on a DomU paravitualized

http://bugzilla.novell.com/show_bug.cgi?id=557745 http://bugzilla.novell.com/show_bug.cgi?id=557745#c14 MARTINEAU Antony changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |FIXED --- Comment #14 from MARTINEAU Antony 2009-12-08 09:17:44 UTC --- Ok thank you -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

5261

Age (days ago)

5276

Last active (days ago)

List overview

Download

13 comments

1 participants

participants (1)

bugzilla_noreply＠novell.com

[Bug 557745] New: Write on a XFS formated logical volume after a snapshot (lvm2) on a DomU paravitualized

tags

participants (1)