search for: unmount

...e LVM volumes for /, /var, /var/lib/mysql etc. System boot proceeds without a hiccup, in terminal systemctl status says everything is OK and running, journalctl says so as well - systemd mounts everything stated in fstab. However, on reboot systemd echoes problems with filesystem on /var : ...// unmounting all volumes Nov 26 23:51:30 www6 systemd[1]: Unmounting /var... Nov 26 23:51:30 www6 umount[2118]: umount: /var: target is busy. Nov 26 23:51:30 www6 systemd[1]: Stopped target Swap. Nov 26 23:51:30 www6 systemd[1]: Deactivating swap /dev/disk/by-label/lv_swap... Nov 26 23:51:30 www6 systemd[1]...

I am receiving these errors when rebooting my system. Unmounting file systems: (1785) ERROR: unable to sendmsg, error=-101, Linux/ocfsipc.c, 394 (1785) ERROR: status = -999, Linux ocfsipc.c, 206 ocfs: Unmounting device (104,33) on rac1-priv1.collo.corp.net (node 2) (1785) ERROR: unable to sendmsg, error=-101, Linux/ocfsipc.c, 394 (1785) ERROR: status = -...

...i Simchoni to make the snapshots mounted outside of the share working [1] and [2]). Everything is working fine, and on Windows the “Previous version" tab allows to restore files from the snapshot. However, when a large file (say 10GB) is being restored, during that time it is not possible to unmount the snapshot block device, because Samba is holding open file descriptors on its mount point. Question: is there a way to forcefully unmount the snapshot block device, such that all ongoing Restore operations will fail? I did some debugging and saw that during the Restore process shadow_copy2_fsta...

Hi Jeremy, The use case is that we want to automatically rotate the snapshots. For example, we want to keep 24 hourly snapshots, and every hour we create a new snapshot and unmount the oldest one. But since customers can be restoring from the oldest snapshot right now, it is not deterministic when we will be able to unmount the oldest snapshot. So at that moment we want all active restore operations to abort with an error, and then we unmount. This problem should be common to...

...l etc. > > System boot proceeds without a hiccup, in terminal systemctl status says > everything is OK and running, journalctl says so as well - systemd > mounts everything stated in fstab. > > However, on reboot systemd echoes problems with filesystem on /var : > > ...// unmounting all volumes > > Nov 26 23:51:30 www6 systemd[1]: Unmounting /var... > Nov 26 23:51:30 www6 umount[2118]: umount: /var: target is busy. > Nov 26 23:51:30 www6 systemd[1]: Stopped target Swap. > Nov 26 23:51:30 www6 systemd[1]: Deactivating swap > /dev/disk/by-label/lv_swap... &...

...kfs.btrfs -f /dev/sdb2 ... unable to open /dev/sdb2: Device or resource busy because mkfs.btrfs tries to open the device O_EXCL, and somebody still has it. Using systemtap to track bdev gets & puts shows a kworker thread doing a blkdev put after mkfs attempts a get; this is left over from the unmount. Adding an rcu_barrier() to btrfs_close_devices() causes unmount to wait until all blkdev_put()s are done, and the device is truly free once unmount completes. Signed-off-by: Eric Sandeen <sandeen@redhat.com> --- p.s. I debated putting it into close_ctree(); I don''t know if there&...

Hi Uri, Thanks for your response. We do not want to delete the share in smb.conf and later to reconfigure it without the shadow copy. We want to keep the shadow copy and rotate the snapshots. For example, we want to keep 24 hourly snapshots, and every hour we create a new snapshot and unmount the oldest one. But since customers can be restoring from the oldest snapshot right now, it is not deterministic when we will be able to unmount the oldest snapshot. So at that moment we want all active restore operations to abort with an error, and then we unmount. Like I mentioned, failing shadow...

Hi All, How do I unmount an NFS share when the NFS server is unaivalable? I tried "umount /bck" but it "hangs" indefinitely "umount -f /bck" tells me the mount if busy and I can't unmount it: root at saturn:[~]$ umount -f /bck umount2: Device or resource busy umount: /bck: device is busy...

The patch titled Subject: ocfs2: fix use-after-free when unmounting read-only filesystem has been added to the -mm mm-hotfixes-unstable branch. Its filename is ocfs2-fix-use-after-free-when-unmounting-read-only-filesystem.patch This patch will shortly appear at https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/ocfs2-fix-use...

...irtualBox was not empty. looking at it I did not see anything in it so I just deleted the directory and say told zfs to Mount it again. This worked fine. Everything shows up mounted fine. The directory is empty though. Not really a problem since I still have the data so I thought I would just unmount the thing and start again. >zfs unmount rpool/export/home/nxn/.VirtualBox cannot unmount ''/export/home/nxn/.VirtualBox/VDI'': Invalid argument >zfs unmount rpool/export/home/nxn/.VirtualBox/VDI cannot unmount ''/export/home/nxn/.VirtualBox/VDI'': Invalid...

Is it practical to get a R/W file handle opened against an existing file on an unmounted ext2 filesystem? -- Chuck Wolber Electronic Flight Bag Crew Information Systems/ Linux Wonk 253.576.1154 "You can't connect the dots looking forward; you can only connect them looking backwards." --Steve Jobs

when you have something smbmounted with samba.. //ADMINISTRATOR@CALVIN_SR/M$ 112G 71G 41G 64% /mnt/samba and you unmount it and it gives you /mnt/samba is busy Im absolutely positive that I am NOT in the /mnt/samba dir, nor is anyone else. is there any way to force it to unmount? Jason

I''m running into a situation where I can''t unmount a mounted snapshot. It shows "busy" even though neither lsof nor fuser show any open files. Umount -f doesn''t work although umount -l does. Is there anything else I can do to debug this scenario or to clear the busy status myself? Or am I down to rebooting each time? This...

Hi all: I am using Centos 5.1. But now I have a problem when unmount a removable usb hard disk with right click and choose unmount volume command. When I did that, system reminds me with a message like this:Cannot unmount volume "xxx", Detail: Cannot remove directory, "xxx" represents a temporary directory made when the system auto mount the disk...

Using the Disk Management GUI. I mounted the floppy copied a file to it by dragging from one Nautilus window to another Then I tried to unmount the floppy and got an error that the device (/media/floppy) was busy. This is not the first time this has happened to me. And it does not happen all the time. In fact, yesterday I did the exact same steps with no problem.

I'm trying to understand why a normal user is not allowed to unmount their USB stick? I think it is most likely a udev rule. does anyone know ? Thanks Phil.

....org (including two laptops) and everything seems to be working fine. Our only concern is for our two public servers. They run linux 2.2.19 for stability reasons. On one of the laptops (dual booting 2.2.19 and 2.4.14) kernel 2.2.19 failed to mount (as ext2, the kernel was not patched) a cleanly unmounted ext3 root partition (cleanly unmounted by 2.4.14). I can't reproduce the problem at the time being (the laptop is being used as a second Xinerama head at the moment), but I will report what messages we get. Has anybody had positive experience in mounting ext3 partitions as ext2 after a clea...

...irectory? We have a test environment managed under puppet that is also our DR environment. In a DR scenario we''ll be umounting all NFS shares from out test array and remounting to our DR array. However, as this is a test environment we have users logged on, so when Puppet attempts to unmount the test directories, it fails with "umount: /test/dir: device is busy" if I fuser against the /test/dir directory and kill the PID all is OK. I need a method of either forcibly umounting the array, or killing all PID''s using the mounted directores so Puppet can unmount them...

...5.0G 3.9G 880M 82% / tmpfs 5.9G 276K 5.9G 1% /dev/shm /dev/sda1 485M 116M 344M 26% /boot /dev/mapper/vg_mei-lv_earthvar 3.0G 748M 2.1G 27% /var /dev/mapper/vg_mei-lv_bacteriaroot 5.0G 3.9G 880M 82% / I tried to unmount the device, but as shown below, it is busy. [root at earth ~]# umount /dev/mapper/vg_mei-lv_bacteriaroot umount: /: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1)) I tried to force unmount the device, but that failed...

...is an updated version v2, which describe more clearly about the case: https://lore.kernel.org/ocfs2-devel/e9fc4b2f-1fcc-7c31-f346-59eccff50f9b at linux.alibaba.com/T/#u Thanks, Joseph On 5/26/23 4:55 AM, Andrew Morton wrote: > The patch titled > Subject: ocfs2: fix use-after-free when unmounting read-only filesystem > has been added to the -mm mm-hotfixes-unstable branch. Its filename is > ocfs2-fix-use-after-free-when-unmounting-read-only-filesystem.patch > > This patch will shortly appear at > https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/t...