bug in ufs?
kostikbel at gmail.com
Mon Jul 6 19:37:00 UTC 2009
On Mon, Jul 06, 2009 at 09:45:45PM +0400, Marat N.Afanasyev wrote:
> Ralf Folkerts wrote:
> >Marat N.Afanasyev wrote:
> >>i have a strange problem with writing data to my ufs2+su filesystem.
> >>1. i made a 1T gpt partition on my storage server, and formatted it:
> >>newfs -U -m 0 -o time -i 32768 /dev/da1p3a
> >>2. i tried to move data from other servers to this filesystem, total
> >>size of files is slightly less than 1T
> >>3. i encountered a 'No space left on device' while i still have 11G of
> >>free space and about 13 million free inodes on the filesystem:
> >>#df -ih
> >>Filesystem Size Used Avail Capacity iused ifree %iused
> >>Mounted on
> >>/dev/da1p3a 1.0T 1.0T 11G 99% 20397465 13363173 60%
> >>all i want to know is whether this is a bug or a feature? and if such
> >>a behavior is well-known, where can i read about it?
> >Hi Marat,
> >just a guess: Are there sparse Files on the Source System that are not
> >being detected by the Tool you used to restore the data? If you used
> >(bsd)tar, did you try -S?
> >A while ago I ran into a similar Problem when copying
> >Oracle-Database-Files (on Linux, though) and the -S - Option came to
> i have a huge amount of small files on the source systems, as you can
> see they have about 20 million files and almost each of them is jpeg or
> gif. afaik, there are no sparse files at all.
> i still cannot figure out what is it: a free space leak in ufs2+su or
> bug in statfs(3), that is used in df, or something else.
My guess that it is due to fragmentation.
As an experiment, try to create 1-byte file. Does it work on the filesystem
in described state ?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090706/bc2c00ad/attachment.pgp
More information about the freebsd-stable