"Raimund Berger" <[email protected]> writes:
> "Robert Rawlins - Think Blue" > <robert.rawlins-EBmHtJ59PSbN/KKgT+RXvNBc4/[email protected]> > writes: > >> Hey Gustin, >> >> Well I tied with the b command argument and get the following output: >> >> voyage:/# du -Pacbx --max-depth=1 . |sort -g >> 0 ./proc > > [snip] > >> 646143009 total >> >> Appears to be very much the same story, 600 off mb used but obviously >> something isnt right. This system is out in the field so I currently >> have no way of placing the card into another system to check it. I'd >> like to avoid having to go and do any manual maintenance on the system >> if possible. >> >> Cheers, >> >> Rob > > Just an idea: before running 'du' you might want to issue a > 'remountrw'. Logic tells me that the mounted tmpfs might be hiding > something which is stored on the real disk and thus escapes 'du'. > > For example the /tmp directory could be loaded with stuff on the disk > you won't see right now due to the tmpfs being mounted over it. > > Regards, R. Addition: just came to think, 'remountrw' won't suffice. You'd need to get rid of the /rw tmpfs mount, which will likely be busy though. Only way around that would be shutting down all processes which access it (or one of the symbolic links pointing to it, like /tmp) and then unmount it. Those processes can found with 'lsof', which hopefully is already installed on your system. An alternative is 'fuser'. Good luck, R. _______________________________________________ Voyage-linux mailing list [email protected] http://list.voyage.hk/mailman/listinfo/voyage-linux
