Hi,
on an EL5 XEN DOM0 system I have following volume
$ df -h /srv Filesystem Size Used Avail Use% Mounted on /dev/sdc1 917G 858G 60G 94% /srv
that partition was used by virtual machines but they were all halted.
service xendomains stop
$ xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 3000 2 r----- 695.1
$ service xend stop
nothing is using the partition $ lsof |grep srv <empty>
$ fuser -m /srv <empty>
$ fuser -km /srv <empty>
but i can not umount /srv
$ umount /srv umount: /srv: device is busy umount: /srv: device is busy
what could keeping the device "busy" ... ?
__ Thanks,
LF
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 22/02/15 14:19, Leon Fauster wrote:
Hi,
on an EL5 XEN DOM0 system I have following volume
$ df -h /srv Filesystem Size Used Avail Use% Mounted on /dev/sdc1 917G 858G 60G 94% /srv
that partition was used by virtual machines but they were all halted.
service xendomains stop
$ xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 3000 2 r----- 695.1
$ service xend stop
nothing is using the partition $ lsof |grep srv <empty>
Run as root: # lsof +D /srv
$ fuser -m /srv <empty>
Again, run this as root. Compare (test example from my system): $ fuser -m /boot 2>/dev/null | wc 0 44 264 # fuser -m /boot 2>/dev/null | wc 0 223 1338
That's 180 processes I'd miss as an ordinary user.
$ fuser -km /srv <empty>
but i can not umount /srv
$ umount /srv umount: /srv: device is busy umount: /srv: device is busy
I'm sure you've checked, but where is your PWD?
what could keeping the device "busy" ... ?
__ Thanks,
LF
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Resent after apparent failure to deliver.
On 22/02/15 14:51, J Martin Rushton wrote:
On 22/02/15 14:19, Leon Fauster wrote:
Hi,
on an EL5 XEN DOM0 system I have following volume
$ df -h /srv Filesystem Size Used Avail Use% Mounted on /dev/sdc1 917G 858G 60G 94% /srv
that partition was used by virtual machines but they were all halted.
service xendomains stop
$ xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 3000 2 r----- 695.1
$ service xend stop
nothing is using the partition $ lsof |grep srv <empty>
Run as root: # lsof +D /srv
$ fuser -m /srv <empty>
Again, run this as root. Compare (test example from my system): $ fuser -m /boot 2>/dev/null | wc 0 44 264 # fuser -m /boot 2>/dev/null | wc 0 223 1338
That's 180 processes I'd miss as an ordinary user.
$ fuser -km /srv <empty>
but i can not umount /srv
$ umount /srv umount: /srv: device is busy umount: /srv: device is busy
I'm sure you've checked, but where is your PWD?
what could keeping the device "busy" ... ?
__ Thanks,
LF
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Am 22.02.2015 um 15:51 schrieb J Martin Rushton martinrushton56@btinternet.com:
on an EL5 XEN DOM0 system I have following volume
$ df -h /srv Filesystem Size Used Avail Use% Mounted on /dev/sdc1 917G 858G 60G 94% /srv
that partition was used by virtual machines but they were all halted.
service xendomains stop
$ xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 3000 2 r----- 695.1
$ service xend stop
nothing is using the partition $ lsof |grep srv <empty>
Run as root: # lsof +D /srv
okay - i will try this scan before booting next time.
$ fuser -m /srv <empty>
Again, run this as root. Compare (test example from my system): $ fuser -m /boot 2>/dev/null | wc 0 44 264 # fuser -m /boot 2>/dev/null | wc 0 223 1338
That's 180 processes I'd miss as an ordinary user.
yep - all my commands were executed as root user (sorry for the $ vs. # confusion)
$ fuser -km /srv <empty>
but i can not umount /srv
$ umount /srv umount: /srv: device is busy umount: /srv: device is busy
I'm sure you've checked, but where is your PWD?
I am also not sitting on the device :-)
-- Thanks
LF
nothing is using the partition $ lsof |grep srv
<empty>
Although the prompt is a $, I assume you're actually doing this as root?
$ umount /srv umount: /srv: device is busy umount: /srv: device is busy
what could keeping the device "busy" ... ?
Is the device NFS exported? I've seem that prevent umounting even though nothing shows up in the process list.
Am 22.02.2015 um 16:12 schrieb Stephen Harris lists@spuddy.org:
nothing is using the partition $ lsof |grep srv
<empty>
Although the prompt is a $, I assume you're actually doing this as root?
Yeah - its a bad behaviour doing tasks with a # prompt and then making a request in mailinglists with $ as prompt. Sorry for that.
$ umount /srv umount: /srv: device is busy umount: /srv: device is busy
what could keeping the device "busy" ... ?
Is the device NFS exported? I've seem that prevent umounting even though nothing shows up in the process list.
Its a local "virtual" device (raid controller exports it as one device).
-- LF
On 02/25/2015 07:48 AM, Leon Fauster wrote:
Am 22.02.2015 um 16:12 schrieb Stephen Harris lists@spuddy.org:
Is the device NFS exported? I've seem that prevent umounting even though nothing shows up in the process list.
Its a local "virtual" device (raid controller exports it as one device).
I believe that Stephen was asking if you are exporting that filesystem via NFS to other systems. Check /etc/exports.