Re: /var/spool/qdaemon 95% full... but nothing in it !

From: Phil Langerholc (root_at_localhost.nospam)
Date: 08/27/05


Date: Sat, 27 Aug 2005 02:26:32 GMT

Fil wrote:
> "Phil Langerholc" <root@localhost.nospam> a écrit dans le message de
> news:uOlPe.4211$p32.330@trndny06...
>
>>Fil wrote:
>>
>>>Hello,
>>>
>>>my FS /var/spool/qdaemon is 95% (of 1 GB) full but when i check it,
>
> there's
>
>>>nothing in it !
>>>I tried to stopsrc / startsrc qdaemon... lpd... spooler... umount the
>
> FS,
>
>>>mount in again... nothing, it's allways 95% full.
>>>
>>>Perhaps a process is locking something or a deleted file stays in a
>
> "ghost"
>
>>>state.
>>>
>>>The easiest way to unlock the problem could be to reboot but it's my
>
> 7d/7
>
>>>production server
>>>
>>>If you have an idea...
>>>Thanks in advance
>>>
>>>Philippe
>>>
>>>
>>
>>Try and fuser -u against the file. You can then see what process has it
>>locked.
>>
>>---Phil
>
>
>
> I've already tried this... but no answer !
>
Are you running it against the /dev/<lvname> for your filesystem? I
find your problem a bit odd, especially if you say you can unmount the
filesystem (if a process is locked on a filesystem it will not allow it
to unmount). Have you tried find /var/spool/qdeamon -xdev -ls? perhaps
there is another file there. If you have lsof you might want to run it
against the filesystem to and check the output (you might find something
in the lost+found directory).

---Phil



Relevant Pages

  • Re: Unmounting by filesystem ID
    ... > The patch below adds a new mount flag MNT_BYFSID that can be used ... > to unmount a filesystem by specifying its filesystem ID instead of ... > filesystem got unmounted, it does not require a reboot to unmount ... this patch only affects unmounting; ...
    (freebsd-arch)
  • Re: Filesystem wont unmount
    ... Subject: Filesystem won't unmount ... Once I came across a filesystem that would not umount, ... copying of this e-mail and/or any attachments thereto, ...
    (AIX-L)
  • Unmounting by filesystem ID
    ... to unmount a filesystem by specifying its filesystem ID instead of ... filesystem got unmounted, it does not require a reboot to unmount ... -getmntname(const char *fromname, const char *onname, ...
    (freebsd-arch)
  • [PATCH] Fix dcache race during umount
    ... between unmounting a filesystem and the memory shrinker. ... prune_dcacheignoring any dentry for which the superblock is being unmounted ... that is being unmounted, and unmount will not be able to start until any such ...
    (Linux-Kernel)
  • Re: 5.1-BETA umount problems
    ... it also makes it easy to shoot ... >yourself in the foot. ... unmount() so that filesystems can be unmounted by specifying the ... filesystem ID instead of a path. ...
    (freebsd-current)