Tag Info

New answers tagged

0

When you say "move" I assume you are talking about using cp or mv to move data from one LV to another, not taking snapshots. In that case, the data is physically moved on disk.


0

According to the docs, busybox 1.12.1 has vi. Anyway, here's your sed regex: sed -i "s/filter\ \=\ \[\ \"a\/loop2\/\",\ \"r\/\.\*\/\"\ \]/filter = [ \"a\/.*\/\" ]/" /etc/lvm/lvm.conf


1

A bit confused here - is it mdadm raid or lvm raid? In the question you mention lvm raid, yet keep trying to use mdadm raid. for lvm - first use pvscan -u possibly pvscan -a --cache /dev/sdc /dev/sdd would be enough to recreate your device. if not, use vgchange -ay VolGroup00 or vgcfgrestore VolGroup00 The other possibility is that you used ...


0

So there is yet another possibility other than NFS, stale bash process and udev misbehaviour, namely partitions opened on the block device. kpartx -d /dev/vg1/lv1 Then you can verify that # open drops to 0 in lvdisplay's output.


0

Your kernel is probably missing dm-snapshot.ko module. You can check that by running: find /lib/modules | grep snapshot to see if any of the kernels installed have that module available. There was a bug at ubuntu, so you should probably be running at least 3.2.0-49.75 to try to avoid that problem. Anyway try kernel upgrade and reboot.


0

This is a duplicate of: Why did rebooting cause one side of my ZFS mirror to become UNAVAIL? In your case, the device names or symbolic links in the /dev/disk-by-* directory on your system were either not present or were renamed. It's best to use /dev/disk-by-id devices for your zpool instead of by-path, as the path names can change. (grrrr... Ubuntu udev) ...


1

I had the same problem and finally solved The problem seems to be in update-initramfs that doesn't generate the initrd properly. "evms_activate not found" means that the /sbin/evms_activate file is not created inside the initrd file by update-initramfs So, my workaround consists in unpacking the not working initrd, and copy the evms_activate executable ...


0

You likely are seeing a situation where at least one of your used disks became unavailable. This might be intermittent and resolvable, both Linux implementations (ZFS on Linux as well as zfs-fuse) seem to exhibit occasional hiccups which are easily cured by a zpool clear or a zpool export / zpool import cycle. As for your question, yes, ZFS is perfectly ...


3

I got into similar situation, but removing of LV was blocked, because I was using mount -o bind. The article below helped a lot, using lsof with major/minor numbers of LV showed process holding opened LV, in my case smbd. Than just simply cat /proc/mounts | grep LV_name led me to conclusion, why lvremove or dmsetup remove refuse to get a rid of unmounted ...


0

I had this problem too. In the end this is what seemed to fix it: diff -u /usr/share/initramfs-tools/scripts/local-top/lvm2-backup /usr/share/initramfs-tools/scripts/local-top/lvm2 --- /usr/share/initramfs-tools/scripts/local-top/lvm2-backup 2014-06-06 19:55:19.249857946 -0400 +++ /usr/share/initramfs-tools/scripts/local-top/lvm2 2014-06-21 ...


1

The meaning of the o in the output of lvs is described in its manpage, under the lv_attrs attributes section: 6 device (o)pen Basically this means the device has been mounted.


0

I encountered this problem just yesterday. I have filesystem(LVM(MD(sda, sdb, sdc-syncing-only-weekly-basis))) configuration on Linux, and needed to access old data on sdc. I somewhat solved the issue by attaching backup disk (sdc) to a VM. This is a safe operation as long as I attach the disk with "qemu ... -drive file=/dev/sdc,readonly" (or use a snapshot ...


0

Well, after several hours of try, get a solution. pvcreate --uid "mising_uid_old_disk" --retorefile /etc/lvm/archive/<latets__file_with_correct_data>.vg /dev/<partition_of_new_disk_replace_old_disk" After this action, you must remove all LV with problem (lost data on old disk)


3

Start over, initialize the disks again with new LVM VGs and restore from backup.


0

Cloning a disk completely confuses lvm. I made an exact copy (with dd) of a LVM partition onto another disk, and lvm started using the copy instead of the original!



Top 50 recent answers are included