* [linux-lvm] How to build LVM2 tools for 2.6? @ 2003-12-22 12:14 Charles Martin 2003-12-22 16:12 ` [linux-lvm] umount returns device is busy P. Larry Nelson 2003-12-23 1:01 ` [linux-lvm] How to build LVM2 tools for 2.6? Luca Berra 0 siblings, 2 replies; 7+ messages in thread From: Charles Martin @ 2003-12-22 12:14 UTC (permalink / raw) To: linux-lvm I'm running Linux 2.6.0 on a system that started life as Red Hat 9. I want to install the LVM2 tools (v2.0.8) so that I can resurrect my LVM disks. When I attempt to build the tools (./configure; make install), device/dev-io.c fails to compile, due to a missing definition of BLKGETSIZE64. Clearly, the compile needs to be looking at the headers in the 2.6.0 tree. I've seen plenty of mention of people running LVM2 successfully with the 2.6 test kernels. Can anyone tell me how to build the tools? Thanks, Charlie ^ permalink raw reply [flat|nested] 7+ messages in thread
* [linux-lvm] umount returns device is busy 2003-12-22 12:14 [linux-lvm] How to build LVM2 tools for 2.6? Charles Martin @ 2003-12-22 16:12 ` P. Larry Nelson 2003-12-22 17:16 ` Herbert Poetzl 2003-12-23 1:01 ` [linux-lvm] How to build LVM2 tools for 2.6? Luca Berra 1 sibling, 1 reply; 7+ messages in thread From: P. Larry Nelson @ 2003-12-22 16:12 UTC (permalink / raw) To: linux-lvm I've been using LVM now since sometime this past summer and everything has worked great and as advertised, until I tried to unmount a logical volume. And this happens on both RedHat 9 and ES_3. I had occasion the other day to unmount one of the mounted raid arrays in order to upgrade some firmware. When I tried to do an unmount command, I got "device is busy". Ok, I'm cd'd there from one of my windows or something, so I make sure all open terminal windows are *not* cd'd there. Redo the umount command with same result. Weird, something's got a file open. So, I did an lsof command and grep for the device (/dev/VG1/LV1). Nothing. I try greping for the mount name (/scratch/cdf). Nothing. It will not let me unmount the logical volume. The system in question is running RedHat 9 w/kernel 2.4.20-24.9smp with RedHat's lvm-1.0.3-12. I just so happened to have built another system using RedHat's ES_3 w/kernel 2.4.21-4.0.1.ELsmp and their lvm-1.0.3-15, so I thought I'd try it there. Built an identical logical volume, mounted it, tested it (works fine), tried to umount the filesystem with identical results: device is busy. Checked again using lsof. Nothing open on the mounted filesystem. I went checking back thru about 4 months of this list and saw (apparently) that no one else has this problem. At this point I'm a bit baffled why the umount command isn't working. I've also seen nothing that might address this in the LVM-HOWTO. Then again, I could have missed it. Ideas? Thanks! -- P. Larry Nelson (217-244-9855) | Systems/Network Administrator 461 Loomis Lab | U of I, CITES Departmental Services 1110 W. Green St., Urbana, IL | Consultant to: High Energy Physics Group MailTo:lnelson@uiuc.edu | http://www.uiuc.edu/ph/www/lnelson ------------------------------------------------------------------------- "Information without accountability is just noise." - P.L. Nelson ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [linux-lvm] umount returns device is busy 2003-12-22 16:12 ` [linux-lvm] umount returns device is busy P. Larry Nelson @ 2003-12-22 17:16 ` Herbert Poetzl 2003-12-22 18:07 ` Spam 2003-12-23 9:52 ` P. Larry Nelson 0 siblings, 2 replies; 7+ messages in thread From: Herbert Poetzl @ 2003-12-22 17:16 UTC (permalink / raw) To: P. Larry Nelson; +Cc: linux-lvm On Mon, Dec 22, 2003 at 04:10:27PM -0600, P. Larry Nelson wrote: > I've been using LVM now since sometime this past summer and > everything has worked great and as advertised, until I tried > to unmount a logical volume. And this happens on both RedHat > 9 and ES_3. > > I had occasion the other day to unmount one of the mounted raid > arrays in order to upgrade some firmware. When I tried to do an > unmount command, I got "device is busy". Ok, I'm cd'd there > from one of my windows or something, so I make sure all open > terminal windows are *not* cd'd there. Redo the umount command > with same result. Weird, something's got a file open. So, I did > an lsof command and grep for the device (/dev/VG1/LV1). Nothing. > I try greping for the mount name (/scratch/cdf). Nothing. > It will not let me unmount the logical volume. > > The system in question is running RedHat 9 w/kernel 2.4.20-24.9smp > with RedHat's lvm-1.0.3-12. I just so happened to have built > another system using RedHat's ES_3 w/kernel 2.4.21-4.0.1.ELsmp and > their lvm-1.0.3-15, so I thought I'd try it there. Built an identical > logical volume, mounted it, tested it (works fine), tried to umount > the filesystem with identical results: device is busy. Checked > again using lsof. Nothing open on the mounted filesystem. > > I went checking back thru about 4 months of this list and saw > (apparently) that no one else has this problem. At this point > I'm a bit baffled why the umount command isn't working. I've > also seen nothing that might address this in the LVM-HOWTO. > Then again, I could have missed it. > > Ideas? maybe some kernel service is holding a reference to that device, nfs or samba server comes to mind, just try to disable them one after the other and see if umount will work ... HTH, Herbert > > Thanks! > -- > P. Larry Nelson (217-244-9855) | Systems/Network Administrator > 461 Loomis Lab | U of I, CITES Departmental Services > 1110 W. Green St., Urbana, IL | Consultant to: High Energy Physics Group > MailTo:lnelson@uiuc.edu | http://www.uiuc.edu/ph/www/lnelson > ------------------------------------------------------------------------- > "Information without accountability is just noise." - P.L. Nelson > > _______________________________________________ > linux-lvm mailing list > linux-lvm@sistina.com > http://lists.sistina.com/mailman/listinfo/linux-lvm > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [linux-lvm] umount returns device is busy 2003-12-22 17:16 ` Herbert Poetzl @ 2003-12-22 18:07 ` Spam 2003-12-23 3:25 ` Frank Benkstein 2003-12-23 9:52 ` P. Larry Nelson 1 sibling, 1 reply; 7+ messages in thread From: Spam @ 2003-12-22 18:07 UTC (permalink / raw) To: Herbert Poetzl > On Mon, Dec 22, 2003 at 04:10:27PM -0600, P. Larry Nelson wrote: >> I've been using LVM now since sometime this past summer and >> everything has worked great and as advertised, until I tried >> to unmount a logical volume. And this happens on both RedHat >> 9 and ES_3. >> >> I had occasion the other day to unmount one of the mounted raid >> arrays in order to upgrade some firmware. When I tried to do an >> unmount command, I got "device is busy". Ok, I'm cd'd there >> from one of my windows or something, so I make sure all open >> terminal windows are *not* cd'd there. Redo the umount command >> with same result. Weird, something's got a file open. So, I did >> an lsof command and grep for the device (/dev/VG1/LV1). Nothing. >> I try greping for the mount name (/scratch/cdf). Nothing. >> It will not let me unmount the logical volume. >> >> The system in question is running RedHat 9 w/kernel 2.4.20-24.9smp >> with RedHat's lvm-1.0.3-12. I just so happened to have built >> another system using RedHat's ES_3 w/kernel 2.4.21-4.0.1.ELsmp and >> their lvm-1.0.3-15, so I thought I'd try it there. Built an identical >> logical volume, mounted it, tested it (works fine), tried to umount >> the filesystem with identical results: device is busy. Checked >> again using lsof. Nothing open on the mounted filesystem. >> >> I went checking back thru about 4 months of this list and saw >> (apparently) that no one else has this problem. At this point >> I'm a bit baffled why the umount command isn't working. I've >> also seen nothing that might address this in the LVM-HOWTO. >> Then again, I could have missed it. >> >> Ideas? > maybe some kernel service is holding a reference > to that device, nfs or samba server comes to mind, > just try to disable them one after the other and > see if umount will work ... In my opinion this is a severe mis-feature (aka: bug) in the Linux kernels. In some occasions it is impossible to kill an application when unmounting a filesystem. This leads to problems with shutting down the system cleanly. For example a device might have been temporary offline when samba tried to access it. The samba thread locks indefinitely and it is impossible to kill it and thus also impossible to unmount the filesystem. Not sure if LVM guys can do anything about this though. =) Perhaps you can push kernel developers to make it easier to recover from these kinds of problems? > HTH, > Herbert ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [linux-lvm] umount returns device is busy 2003-12-22 18:07 ` Spam @ 2003-12-23 3:25 ` Frank Benkstein 0 siblings, 0 replies; 7+ messages in thread From: Frank Benkstein @ 2003-12-23 3:25 UTC (permalink / raw) To: linux-lvm On Tue, 23 Dec 2003 01:06:08 +0100 Spam <spam@tnonline.net> wrote: > > > > On Mon, Dec 22, 2003 at 04:10:27PM -0600, P. Larry Nelson wrote: > >> I've been using LVM now since sometime this past summer and > >> everything has worked great and as advertised, until I tried > >> to unmount a logical volume. And this happens on both RedHat > >> 9 and ES_3. > >> > >> I had occasion the other day to unmount one of the mounted raid > >> arrays in order to upgrade some firmware. When I tried to do an > >> unmount command, I got "device is busy". Ok, I'm cd'd there > >> from one of my windows or something, so I make sure all open > >> terminal windows are *not* cd'd there. Redo the umount command > >> with same result. Weird, something's got a file open. So, I did > >> an lsof command and grep for the device (/dev/VG1/LV1). Nothing. > >> I try greping for the mount name (/scratch/cdf). Nothing. > >> It will not let me unmount the logical volume. > >> > >> The system in question is running RedHat 9 w/kernel 2.4.20-24.9smp > >> with RedHat's lvm-1.0.3-12. I just so happened to have built > >> another system using RedHat's ES_3 w/kernel 2.4.21-4.0.1.ELsmp and > >> their lvm-1.0.3-15, so I thought I'd try it there. Built an > >identical> logical volume, mounted it, tested it (works fine), tried > >to umount> the filesystem with identical results: device is busy. > >Checked> again using lsof. Nothing open on the mounted filesystem. > >> > >> I went checking back thru about 4 months of this list and saw > >> (apparently) that no one else has this problem. At this point > >> I'm a bit baffled why the umount command isn't working. I've > >> also seen nothing that might address this in the LVM-HOWTO. > >> Then again, I could have missed it. > >> > >> Ideas? > > > maybe some kernel service is holding a reference > > to that device, nfs or samba server comes to mind, > > just try to disable them one after the other and > > see if umount will work ... > > In my opinion this is a severe mis-feature (aka: bug) in the Linux > kernels. In some occasions it is impossible to kill an application > when unmounting a filesystem. This leads to problems with shutting > down the system cleanly. For example a device might have been > temporary offline when samba tried to access it. The samba thread > locks indefinitely and it is impossible to kill it and thus also > impossible to unmount the filesystem. > > Not sure if LVM guys can do anything about this though. =) Perhaps > you can push kernel developers to make it easier to recover from > these kinds of problems? > Have you tried "fuser -v -m" (see fuser(1)). I think "umount -l" already serves the your case of unmounting a filesystem where kernel thinks it's busy but it isn't. Bye Frank Benkstein. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [linux-lvm] umount returns device is busy 2003-12-22 17:16 ` Herbert Poetzl 2003-12-22 18:07 ` Spam @ 2003-12-23 9:52 ` P. Larry Nelson 1 sibling, 0 replies; 7+ messages in thread From: P. Larry Nelson @ 2003-12-23 9:52 UTC (permalink / raw) To: Herbert Poetzl, linux-lvm Herbert Poetzl wrote: > > On Mon, Dec 22, 2003 at 04:10:27PM -0600, P. Larry Nelson wrote: > > I've been using LVM now since sometime this past summer and > > everything has worked great and as advertised, until I tried > > to unmount a logical volume. And this happens on both RedHat > > 9 and ES_3. > > > > I had occasion the other day to unmount one of the mounted raid > > arrays in order to upgrade some firmware. When I tried to do an > > unmount command, I got "device is busy". Ok, I'm cd'd there > > from one of my windows or something, so I make sure all open > > terminal windows are *not* cd'd there. Redo the umount command > > with same result. Weird, something's got a file open. So, I did > > an lsof command and grep for the device (/dev/VG1/LV1). Nothing. > > I try greping for the mount name (/scratch/cdf). Nothing. > > It will not let me unmount the logical volume. > > > > The system in question is running RedHat 9 w/kernel 2.4.20-24.9smp > > with RedHat's lvm-1.0.3-12. I just so happened to have built > > another system using RedHat's ES_3 w/kernel 2.4.21-4.0.1.ELsmp and > > their lvm-1.0.3-15, so I thought I'd try it there. Built an identical > > logical volume, mounted it, tested it (works fine), tried to umount > > the filesystem with identical results: device is busy. Checked > > again using lsof. Nothing open on the mounted filesystem. > > > > I went checking back thru about 4 months of this list and saw > > (apparently) that no one else has this problem. At this point > > I'm a bit baffled why the umount command isn't working. I've > > also seen nothing that might address this in the LVM-HOWTO. > > Then again, I could have missed it. > > > > Ideas? > > maybe some kernel service is holding a reference > to that device, nfs or samba server comes to mind, > just try to disable them one after the other and > see if umount will work ... > > HTH, > Herbert That was it. The nfs daemon had it tied up (we're not running samba). I tried 'umount -f' and 'umount -l' without success. Frank Benkstein suggested using 'fuser -v -m /scratch/cdf' and that returned nothing as well. But when I stopped the nfs daemon, it unmounted just fine. On a hunch, further testing shows that it's not necessary to actually stop the nfs daemon, just remove the entry from /etc/exports for the filesystem you wish to unmount and run 'exportfs -r'. That way, apparently, the nfs daemon no longer cares what you do with the filesystem. Then, the umount command works just fine. But it is interesting that fuser doesn't indicate that nfsd has a hold on the mounted filesystem. Thanks to all! - Larry -- P. Larry Nelson (217-244-9855) | Systems/Network Administrator 461 Loomis Lab | U of I, CITES Departmental Services 1110 W. Green St., Urbana, IL | Consultant to: High Energy Physics Group MailTo:lnelson@uiuc.edu | http://www.uiuc.edu/ph/www/lnelson ------------------------------------------------------------------------- "Information without accountability is just noise." - P.L. Nelson ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [linux-lvm] How to build LVM2 tools for 2.6? 2003-12-22 12:14 [linux-lvm] How to build LVM2 tools for 2.6? Charles Martin 2003-12-22 16:12 ` [linux-lvm] umount returns device is busy P. Larry Nelson @ 2003-12-23 1:01 ` Luca Berra 1 sibling, 0 replies; 7+ messages in thread From: Luca Berra @ 2003-12-23 1:01 UTC (permalink / raw) To: linux-lvm On Mon, Dec 22, 2003 at 11:12:43AM -0700, Charles Martin wrote: >I'm running Linux 2.6.0 on a system that >started life as Red Hat 9. I want to install >the LVM2 tools (v2.0.8) so that I can resurrect >my LVM disks. > >When I attempt to build the tools (./configure; make install), >device/dev-io.c fails to compile, due to a missing definition >of BLKGETSIZE64. Clearly, the compile needs to be looking >at the headers in the 2.6.0 tree. > try this patch i stole from fedora :) or use their rpm L. --- LVM2.2.00.08/lib/device/dev-io.c.blksize64 2003-12-02 19:00:00.347446473 -0500 +++ LVM2.2.00.08/lib/device/dev-io.c 2003-12-02 19:00:42.450641542 -0500 @@ -23,6 +23,9 @@ # undef WUNTRACED /* Avoid redefinition */ # include <linux/fs.h> /* For block ioctl definitions */ # define BLKSIZE_SHIFT SECTOR_SHIFT +#ifndef BLKGETSIZE64 +# define BLKGETSIZE64 _IOR(0x12,114,size_t) +#endif /* BLKGETSIZE64 */ #else # include <sys/disk.h> # define BLKBSZGET DKIOCGETBLOCKSIZE -- Luca Berra -- bluca@comedia.it Communication Media & Services S.r.l. /"\ \ / ASCII RIBBON CAMPAIGN X AGAINST HTML MAIL / \ ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2003-12-23 9:52 UTC | newest] Thread overview: 7+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2003-12-22 12:14 [linux-lvm] How to build LVM2 tools for 2.6? Charles Martin 2003-12-22 16:12 ` [linux-lvm] umount returns device is busy P. Larry Nelson 2003-12-22 17:16 ` Herbert Poetzl 2003-12-22 18:07 ` Spam 2003-12-23 3:25 ` Frank Benkstein 2003-12-23 9:52 ` P. Larry Nelson 2003-12-23 1:01 ` [linux-lvm] How to build LVM2 tools for 2.6? Luca Berra
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.