similar to: 'umount' of multi-device volume hangs until the device is physically un-plugged

Add the option force and lazy for force and lazy umount. Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com> --- daemon/mount.c | 25 +++++++++++++++++++++++-- generator/generator_actions.ml | 23 ++++++++++++----------- gobject/Makefile.inc | 2 ++ po/POTFILES | 1 + 4 files changed, 38 insertions(+), 13 deletions(-) diff --git

When unmounting all filesystems, it appears that large amounts of writes in flight + very slow storage may cause the umount command to fail temporarily. Even the briefest of pauses appears to let the umount succeed. In this patch, call umount as normal, but if it fails, wait a few seconds then call it again (if it fails a second time, we report the error and fail the operation). I considered

Add the option force and lazy for force and lazy umount. Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com> --- daemon/mount.c | 25 +++++++++++++++++++++++-- generator/generator_actions.ml | 23 ++++++++++++----------- gobject/Makefile.inc | 2 ++ po/POTFILES | 1 + 4 files changed, 38 insertions(+), 13 deletions(-) diff --git

> > Hi, > > I'm running a 2.4.18-14 kernel with a heavy IO profile using > ext3 over RAID 0+1 volumes. > > From time to time I get a black screen stuck machine while > trying to umount a volume during an IO workload (as part of a > failback solution - but after killing all IO processes ), > with ping still responding, but everything else mostly dead. >

> > Hi, > > The problem reproduces on a 2.4.18-19 kernel as well. Took > some more time but finally it roared its ugly head. > > This is the stack trace from the new kernel: > > > c01190b8 f3791eb4 set_running_and_schedule > > c010a8b0 f3791ed0 enable_irq > > c014200c f3791f0c IO_APIC_get_PCI_irq_vector > > c0155595 f3791f0c clear_inode >

I don't see any mention of this in the archives and maybe it's a stupid question but... I have a separate partition for /var and it is an ext3 partiition. When I try to reboot, /etc/rc.d/init.d/halt tries to umount all the filesystems (other than /proc, /, etc) but it fails on attempting to umount /var. I am pretty sure that this is because kjournald is using it. Does anyone have any

Author: casper Repository: /hg/zfs-crypto/gate Revision: b8dc006ee63f520b5db5b6a94d1746a6518ff072 Log message: 6268481 unprivileged user calling umount on a autofs mountpoint hangs Files: update: usr/src/uts/common/fs/autofs/auto_vnops.c

Hello, I''m not sure about this, when a device is set read-only, are journal commit still allowed then, or is this the reason, why the umount hangs forever? [44825.302262] LustreError: Skipped 572 previous similar messages [44882.668079] Lustre: Failing over pfs1work-OST0026 [44882.674578] Lustre: *** setting obd pfs1work-OST0026 device ''unknown-block(9,7)'' read-only

I have an NFS server and NFS client separated by a firewall. Both servers are FreeBSD 7.1. Server configuration: nfs_server_enable="YES" nfs_server_flags="-t -n 4" rpcbind_enable="YES" mountd_flags="-r -p 737" mountd_enable="YES" The firewall allows tcp and udp to port 111, but only tcp to ports 2049 and 737 (configured for mountd, see above).

Any recommendation about the sequence to umount multiple lustre file system with combined MGS/MDT or separate MGS, MDT. Thanks. Ming -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.lustre.org/pipermail/lustre-discuss/attachments/20100909/396905b5/attachment.html

-- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top -------------- next part -------------- >From 490560439061398d47873484a55fb823be29b285 Mon Sep 17 00:00:00 2001 From: Richard W.M. Jones

Hi all, The 'I/O error' subject has passed the mailinglist a few times now, but I couldn't find a solution in the archives. Here is what happened to me; I mounted some windows 98 shares onto my Linux Slackware box. After a while I got the (well-known) I/O error on the mounting point when using ls or df. Normally (it happened to me before) I could just umount or smbumount the mount

Hi all, this is the situation: two linux servers mounting a samba share from each other. Sometimes one of the two share becomes locked, I mean that everything I try to do on it results in an "Input/Output error". I'm then unable to umount the share, since either smbumount or umount report "device or resource busy". Unluckily I cannot check if this is the case, since the

I'm trying to work from the Samba 4 source and SRPM's to build a nice clean Samba package for work, to test some of its features. Overall, I'm happy with what I see, but the new "autogen.sh" seems to construct its "source4/configure" script from these "build" tools, and they entirely ignore the concept of "sbindir" in installing the mount.cifs

Hi My system data: Linux alucard 2.6.24.3 #4 SMP PREEMPT Sat Apr 26 19:36:27 CEST 2008 i686 GNU/Linux I selected the experimental cifs options (but I get the same behaviour with a different kernel where they aren't selected) mount.cifs version: 1.10-3.0.28a (but I also tried an earlier version) ubuntu hardy I bought a netgear ready nas nv+ and enabled a few cifs shares. When I try to mount

In nfsmount, the function mount_call() is used to invoke both the mount and umount PRC's. These take identical arguments, but umount returns void rather than a file handle, so result should not be checked. This avoids a spurious 'incomplete reply' message if mount(2) system call fails. Signed-off-by: Erik van Konijnenburg <ekonijn@xs4all.nl> Index:

Signed-off-by: Sergey Vlasov <vsu at altlinux.ru> --- Alternatively, you may pull from the following git repo and branch: git://git.altlinux.org/people/vsu/packages/klibc.git alt-umount (branch based on the klibc-1.4.32 release - sorry, forgot to send this patch earlier) usr/utils/umount.c | 7 +++++-- 1 files changed, 5 insertions(+), 2 deletions(-) diff --git

OK, I believe this is the cause of the 3 related failures on CentOS / RHEL. Calls to guestfs_umount ("/dev/...") didn't have the device path being rewritten. Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones New in Fedora 11: Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 70 libraries

On Thu, Feb 20, 2014 at 01:47:52PM +0100, Olivier Nicaise wrote: > Hi, > > I am currently having an issue with the libvirt_lxc binary that is launched > when starting a lxc instance using libvirt. This process seems to have its > own namespace for mounts. > What happens is that if I umount something in the global namespace, it > stays mounted in the libvirt_lxc namespace.

With CONFIG_BALLOON_COMPACTION=y, it will mount balloon_mnt for balloon page migration when probe a virtio_balloon device, however do not unmount it when remove the device, fix it. Fixes: b1123ea6d3b3 ("mm: balloon: use general non-lru movable page feature") Signed-off-by: Yisheng Xie <xieyisheng1 at huawei.com> --- drivers/virtio/virtio_balloon.c | 4 ++++ 1 file changed, 4