From: Ross B. <Ros...@st...> - 2007-08-10 17:22:04
|
On Fri, 2007-07-27 at 08:11 -0700, Brock, Anthony - NET wrote: > Is this project still active? This is the third request for help > concerning the snapshot feature from three different individuals > (including myself) in two months. No one has even acknowledged the issue > or problem. This leads me to wonder if anyone is still working on this > project. > > If this project isn't active, what is a recommended alternative to evms? > I'm currently using it to greatly simplify my management of volumes and > virtual machines. In truth, I love it! When it works, it does an > excellent job and simplifies my job. However, I don't want to continue > deploying it if I'm dealing with dead technology. > > Thanks for any advice or info! > > Tony This may be an LVM problem at base; I just found this thread complaining of not being able to delete a snapshot on the LVM list: https://www.redhat.com/archives/linux-lvm/2007-August/msg00010.html https://www.redhat.com/archives/linux-lvm/2007-May/msg00010.html https://www.redhat.com/archives/linux-lvm/2007-March/msg00028.html Both reports are on Debian systems, as am I. The last one says the problem was a kernel issues that was fixed in 2.6.19. Because of video driver support, I have to hold at 2.6.18 for now. So I'm not sure converting from EVMS to straight LVM(2) will solve the problem, or that it is really an EVMS problem. Mostly, I'm just nervous about converting my partitions in place and switching low-level tools underneath me. Ross > > > > -----Original Message----- > > From: Ross Boylan [mailto:ro...@bi...] > > Sent: Thursday, July 26, 2007 10:36 PM > > To: Brock, Anthony - NET > > Cc: ro...@bi...; evm...@li... > > Subject: Re: [Evms-devel] Snapshot feature problems with > > kernel 2.6.21.6 > > > > On Mon, 2007-07-23 at 11:30 -0700, Brock, Anthony - NET wrote: > > > I've recently had to manually update my host kernel on a > > Debian testing > > > system to 2.6.21.6. However, with the upgrade from 2.6.16.27 the > > > snapshot feature with the stock Debian version of evms (2.5.5) isn't > > > working properly: > > > > > > 1. I create a snapshot. > > > 2. I create the volume. > > > 3. I successfully backup the data from the first volume. > > > 4. I delete the volume > > > 5. I attempt to delete the snapshot (fails). > > > > > > However, I can't delete it (it returns a "Device or resource busy"). > > Me too. > > Debian 2.6.18 stock (686) kernel. > > I'm also at evms 2.5.5-22 in testing. > > > > > I see the following in the log: > > > > > > Jul 23 10:57:10 vs2.sterlingcgi.com _2_ BBR: BBR_InitTask: > > > context->action is unknown or unsupported > > I see BBR complaints too. I originally created some of the > > objects with > > an evms and kernel adopted for BBR; I have a feeling that feature may > > have dropped our, or never been in, the stock kernels I'm not using. > > > > However, the volume I am snapshotting is a fairly new object. The > > snapshot is on an old disk from an old system; my current > > root partition > > is the one I'm snapshotting: > > > > EVMS: Query: Objects, Plugin = Snapshot > > > > Object Name: BackSnap > > Major: 0 > > Minor: 0 > > Active: FALSE > > Object Size: 480.00 MB > > > > Object Name: lvm2/daisy/root#origin# > > Major: 254 > > Minor: 12 > > Active: TRUE > > Object Size: 480.00 MB > > > > I can provide more debugging info if it would be helpful. There are a > > lot of other warnings, but they mostly relate to MS Windows > > file systems > > that seemingly have nothing to do with my snapshot. I recall > > investigating these quite awhile ago, and being told the messages were > > not signficant. > > > > I also notice that in the scheduled transactions (when I use > > the GUI) I > > see "reactivate /dev/evms/Root" at the end. This seems odd, since I > > never deactivated it. It is the region being snapshotted. > > > > Here's some chatter logcheck picked up: > > Jul 26 20:21:14 corn kernel: ReiserFS: dm-72: found reiserfs format > > "3.6" with standard journal > > Jul 26 20:21:14 corn kernel: ReiserFS: dm-72: using ordered data mode > > Jul 26 20:21:14 corn kernel: ReiserFS: dm-72: journal params: device > > dm-72, size 8192, journal first block 18, max trans len 1024, > > max batch > > 900, max commit age 30, max trans age 30 > > Jul 26 20:21:14 corn kernel: ReiserFS: dm-72: checking transaction log > > (dm-72) > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: Using r5 hash to sort > > names > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: Removing [15336 > > 13558 0x0 > > SD]..done > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: Removing [15336 > > 13376 0x0 > > SD]..done > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: Removing [15338 > > 13328 0x0 > > SD]..done > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: Removing [15338 > > 13324 0x0 > > SD]..done > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: Removing [15336 > > 13154 0x0 > > SD]..done > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: Removing [15336 > > 13069 0x0 > > SD]..done > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: Removing [15336 > > 13018 0x0 > > SD]..done > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: Removing [15336 > > 12985 0x0 > > SD]..done > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: Removing [15336 > > 12954 0x0 > > SD]..done > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: Removing [15336 > > 12952 0x0 > > SD]..done > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: Removing [15336 > > 12930 0x0 > > SD]..done > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: Removing [15336 > > 12926 0x0 > > SD]..done > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: Removing [15336 > > 12870 0x0 > > SD]..done > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: Removing [15336 > > 12709 0x0 > > SD]..done > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: Removing [15336 > > 12640 0x0 > > SD]..done > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: Removing [15336 > > 10511 0x0 > > SD]..done > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: Removing [15336 > > 10111 0x0 > > SD]..done > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: Removing [15336 9982 0x0 > > SD]..done > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: Removing [15336 9810 0x0 > > SD]..done > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: Removing [15336 6745 0x0 > > SD]..done > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: Removing [15336 3675 0x0 > > SD]..done > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: Removing [26 226 0x0 > > SD]..done > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: Removing [26 225 0x0 > > SD]..done > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: Removing [26 224 0x0 > > SD]..done > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: Removing [26 222 0x0 > > SD]..done > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: Removing [26 218 0x0 > > SD]..done > > Jul 26 20:21:15 corn kernel: ReiserFS: dm-72: There were 26 > > uncompleted > > unlinks/truncates. Completed > > Jul 26 20:22:14 corn kernel: device-mapper: ioctl: unable to > > remove open > > device Root > > Jul 26 20:41:19 corn kernel: device-mapper: ioctl: unable to > > remove open > > device Root > > Jul 26 20:48:47 corn kernel: device-mapper: ioctl: unable to > > remove open > > device Root > > Jul 26 20:54:53 corn kernel: device-mapper: ioctl: unable to > > remove open > > device Root > > Jul 26 20:59:49 corn kernel: device-mapper: ioctl: unable to > > remove open > > device Root > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Evms-devel mailing list > Evm...@li... > To subscribe/unsubscribe, please visit: > https://lists.sourceforge.net/lists/listinfo/evms-devel > |