All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gabriel Barazer" <gabriel@oxeva.fr>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Another XFS + LVM2 snapshots problems
Date: Sat, 22 Apr 2006 16:13:01 +0200	[thread overview]
Message-ID: <003f01c66616$de010400$0100a8c0@inspiron> (raw)

Hello,

Although I often read in the mailing archive that XFS and snapshots aren't 
good friends, this filesystem is the best for my use (a file server with 
~2.5M files and files > 2GB). Now is the time to do snapshots. Here many 
problems occurs :

[hardware detail & software versions on the bottom]

- creating a snapshot with lvcreate -L 10G -n my_backup -s 
/dev/myvg/xfs_storage is OK without using xfs_freeze.

- BUT lvremove the "my_backup" LV (snapshot LV) freeze completely the 
snapshotted LV (xfs_storage in this case). Some days after testing this, i 
found that a simple "dmsetup resume myvg-my_backup" unlock the whole thing 
and lvremove completes.

At this point I was happy to add/remove snapshots freely (but have not tried 
to make multiple snapshot, which kills performances), but now i have a 
snapshot, i can't mount it... here is the scenario :

- lvcreate as shown above
- mount -o nouuid /dev/myvg/my_backup /backups/snapshot

syslog says :
Apr 22 15:14:47 filer1 kernel: XFS mounting filesystem dm-2
Apr 22 15:14:48 filer1 kernel: Starting XFS recovery on filesystem: dm-2 
(logdev: internal)

and nothing else. The I/O activity shown by iostat is the same (no increase 
due to a real XFS recovery)
trying mount -o nouuid,ro does the same. when strace-ing the mount command, 
the last lines are :
open("/dev/myvg/my_backup", O_RDONLY) = 3
lseek(3, 0, SEEK_SET) = 0
read(3, "XFSB\0\0\20\0\0\0\0\0\4\260\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 576) = 
576
close(3) = 0
mount("/dev/myvg/my_backup", "/backups/snapshot/", "xfs", 
MS_RDONLY|0xc0ed0000, 0x517b60 <unfinished ...>

now, i can't kill the mount command initiated neither soft reboot the 
server. I only want to create a snapshot to xfsdump - it , xfsrestore it on 
another backup server, then delete the snapshot.

Does someone here get the same problems ?

Hardware detail:
RAID 10 with 64K stripe on a
3ware 9500S-12 controller and 12x250GB
system is not installed on the LVM (separate RAID 1)

Software versions:
Linux kernel 2.6.16.1
LVM & mapper version 2.01.15 (library 1.01.15, driver version 4.5.0)
XFS utils version 2.7.11
no patches applied, all tools compiled from the official sources

LVM config :
1 VG created from 1 PV (the RAID array is known to the system by /dev/sdb)
some LVs. the LV sizes i want to snapshot are ~200GB each.

-- 
Gabriel Barazer <gabriel@oxeva.fr>
OXEVA 

             reply	other threads:[~2006-04-22 14:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-22 14:13 Gabriel Barazer [this message]
2006-04-22 18:01 ` [linux-lvm] Another XFS + LVM2 snapshots problems Alasdair G Kergon
2006-04-22 19:56   ` Luca Berra
2006-04-22 20:43     ` Alasdair G Kergon

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='003f01c66616$de010400$0100a8c0@inspiron' \
    --to=gabriel@oxeva.fr \
    --cc=linux-lvm@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.