** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1071733
Title:
NFS export of LVM snapshot exports origin instead of snapshot
Status in linux package in Ubuntu:
Fix Released
Bug description:
we're using LVM snapshots on our storage server to provide data for our live
and staging instances.
there are two mountpoints on the server, one for the origin volume, and one
for the snapshot that are exported using NFS to our live/staging instances
(webserver)
today i noticed, that writes on our staging-webserver don't go to the
snapshot as expected, but are hitting the origin volume, messing up
all of our live data.
i checked the NFS-mounts and -exports and they look perfectly valid (staging
mounts snapshot-mountpoint, live mounts origin-mountpoint)
on the storage-server itself looking at the mountpoints, everything looks
valid, too. i wrote some identifying test-files in each mountpoint in order to
track them. no problem as long, as we look on the NFS-server itself.
but looking in the mountpoints of a NFS-client, it shows that the origin data
was mounted.
i found no way to mount the snapshot again.
i'm not entirely sure, what component causes the problem. since the
mountpoints look valid on the server itself, i would rule out LVM. i
also would rule out the NFS-client, since it should not be able to see
what the server hasn't exported. all clients can see the problem
(lucid, maverick, precise).
i've checked for recent software-upgrades on the NFS-server and found:
Thu, Oct 25 2012 11:07:16 +0000
[INSTALL] linux-image-3.2.0-32-generic:amd64
[UPGRADE] nfs-common:amd64 1:1.2.5-3ubuntu3 -> 1:1.2.5-3ubuntu3.1
[UPGRADE] nfs-kernel-server:amd64 1:1.2.5-3ubuntu3 -> 1:1.2.5-3ubuntu3.1
Fri, Oct 26 2012 09:29:34 +0000
[UPGRADE] linux-generic:amd64 3.2.0.31.34 -> 3.2.0.32.35
[UPGRADE] linux-image-generic:amd64 3.2.0.31.34 -> 3.2.0.32.35
since it was working as expected before thursday (2012-10-25), i downgraded
these packages (and rebooted the older kernel)
this didn't solve the problem.
i can reproduce this behavior using different filesystems on the NFS-
server.
i'll attach verision info in my next post. please comment on what info you
might need to figure this out.
---
AlsaDevices:
total 0
crw-rw---T 1 root audio 116, 1 Oct 26 10:56 seq
crw-rw---T 1 root audio 116, 33 Oct 26 10:56 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu14
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=2c4f34e2-4803-4753-98ae-ac398223c2e2
InstallationMedia:
IwConfig: Error: [Errno 2] No such file or directory
MachineType: System manufacturer System Product Name
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-31-generic
root=/dev/mapper/vg0-system ro nomodeset
ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
RelatedPackageVersions:
linux-restricted-modules-3.2.0-31-generic N/A
linux-backports-modules-3.2.0-31-generic N/A
linux-firmware 1.79.1
RfKill: Error: [Errno 2] No such file or directory
StagingDrivers: mei
Tags: precise staging
Uname: Linux 3.2.0-31-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 07/16/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2106
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8B WS
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1071733/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
