[NTLUG:Discuss] Samba disk space reporting -vs- actual usage

[Richard Geoffrion]

> Richard Geoffrion wrote:
>
> > Ok.  So I'm looking at disk space usage on a SAMBA share via the WIndows
98
> > file-folder properties dialog box.
> >
> > The particular directory in question states that the files in that
directory
> > total 18.1 Megabytes(19,681,656 bytes) and that 77,496,320 bytes are
used.
> > So I am correct in determining that 18.1 Meg worth of files are taking
up
> > 73.9 Meg of disk space on my REISERFS partition?
> >
> >
> > hmm...wait...   a 'du -a -h' shows that only 22 Meg is in use.
> >
> >
> > Well, I guess this is not as big an issue as I thought.  Dang it!  Why
the
> > descrepancy?
>
>
> Just a guess, but Windows really doesn't know what to do with symlinks.
> (though I think someone added an option to Samba to disable the read
> through).  So... when Windows sees a symlink... it's the same as a file
> and/or directory (don't put a looping symlink, that is, one that points
> back into the same heirarchy at the same or higher level, in a Samba
> share and try to back it up with a Windows program!).
>
>

Well then that begs the question....How the heck are you supposed to restore
a SAMBA share?  I guess that the backup better be made with a linux backup
utility that can handle the restore.  I'd hate to restore DOUBLE the
information just because the actual data got restored in both the file and
the symlink that pointed to the file.

I am quickly seeing where symlinks on Samba shares are a BAD idea!  Dang
those MS OSes!

The normal everyday non-shell SAMBA users shouldn't be creating symlinks
anyway so I guess that won't be a problem.  I think I do a test later where
disk usage is calculated in a symlink free directory structure.

Thanks for the info, Chris. Gotta run.

-Richard