Attempting to track down a sudden space gobbler (I start the day with 50GB,
and by the afternoon get warnings of disk full; restart and all the space is
reclaimed) I ran "sudo du -sh" from the root immediately after restart, so
that I can run it again later and get a clue to where the data is going.
But du fails with this message:
du: Can't follow symlink cycle from ./dev/fd/3 to ./dev/fd/3
Investigating /dev/fd I find it looks like this:
$ ls -la
total 0
crw--w---- 1 benr tty 16, 0 15 Sep 08:32 0
crw--w---- 1 benr tty 16, 0 15 Sep 08:32 1
crw--w---- 1 benr tty 16, 0 15 Sep 08:32 2
dr--r--r-- 1 root wheel 0 15 Sep 08:22 3
dr--r--r-- 1 root wheel 0 15 Sep 08:22 4
dr--r--r-- 1 root wheel 0 15 Sep 08:22 5
$ ls -la 3
ls: 3: Bad file descriptor
$ ls -la 4
ls: 4: Bad file descriptor
$ ls -la 5
ls: 5: Bad file descriptor
Is this a very bad thing, or just mildly messy? As /dev/fd/3 (and 4 and 5)
are evidently not doing anything useful can I just delete them so that they
don't get in the way of du, or is this a symptom of something more serious
that I need to investigate first?
(NB: I've run a full Disk Utility verify&repair - and there was stuff, beyond
permissions, to repair - but it made no difference to /dev/fd.)
TIA,
Ben
--
You received this message because you are subscribed to the Google Groups "Sussex
Mac User Group" group.
To post to this group, send an email to [email protected].
To unsubscribe from this group, send email to [email protected].
For more options, visit this group at
http://groups.google.com/group/smug?hl=en-GB.
