Thanks for the thought Peter. I'll investigate ._ just to be sure, but the inode explanation has piqued my curiosity. My confusion arise in the discrepancy between df (disk free space) and du (file space usage).
The mount point for /dev/hdc7 (the HFS+ partition) is /mnt/macosx. When mounted, df gives the following output for df -h: Filesystem Size Used Avail Use% Mounted on /dev/hdc8 7.7G 5.9G 1.5G 80% / none 125M 0 125M 0% /dev/shm /dev/hdc10 35G 33G 823M 98% /home /dev/hdc7 25G 23G 2.4G 91% /mnt/macosx sudo du -h --max-depth=1 gives the following output for /mnt/macosx: 14G ./Desktop Folder 651M ./gallery 1.9G ./ydl-backup 17G . The grand total for du is 17G while it's 23G for df. That's ~6G that's missing!!! Now, I'm wondering if ydl-backup could be the problem since it contains files that belong to a specific account. Anyway, I'll back everything up to DVD and wipe (after trying a few bug fixes)... though, maybe I should just wait until 4.1 is out and just start fresh. Having multiple partitions is driving me bonkers. I've had to create more links than I feel comfortable with. Eric. On 1/30/06, Peter-Paul <[EMAIL PROTECTED]> wrote: > I had a same sort of problem with a ext3 partition and I found the > solution in removing al the"hidden" files that were made by OS X client > that connected using SMB. > Apperently this typical "hidden" OS X files took al the space. > For example: > I created a file on my OS X client called test.txt. OS X created also a > file called ._test.txt > Since I deleted the file test.txt on my YDL machine, I didn't delete the > hidden equivalent ._test.txt > > When I manually deleted all the files starting with " ._" I got all my > space back. > I don't know which version of OS X I was running, but I'm sure I ran YDL > 3.0.1 on my server. > > Hope this'll help, good luck, > > Peter. > > Jima wrote: > > > On Sat, 28 Jan 2006, Rick Thomas wrote: > > > >> Just a thought... > >> > >> When you "deleted" the 4.3 GB, are you sure it's really gone? Did it > >> maybe get moved into a trash-bin of some kind, where it's still > >> taking up space? (look for a directory called ".trash" or something > >> like that...) You might try the UNIX "find(1)" utility to look for > >> the "deleted" files by name. If you can find them, they weren't > >> really deleted. > > > > > > Nice thought, but I have another twist to it: might the files have > > been hardlinked someplace else? If there are two files linked to the > > inode, and you delete one, it doesn't delete the other, and release > > the inode. Or something like that. > > > > Jima _______________________________________________ yellowdog-general mailing list [email protected] http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general HINT: to Google archives, try '<keywords> site:terrasoftsolutions.com'
