Ralf Folkerts wrote:
Marat N.Afanasyev wrote:hello!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/da1p3a2. i tried to move data from other servers to this filesystem, total size of files is slightly less than 1T3. 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 -ihFilesystem Size Used Avail Capacity iused ifree %iused Mounted on /dev/da1p3a 1.0T 1.0T 11G 99% 20397465 13363173 60% /mnt/45_114all 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 rescue.Cheers, _ralf_
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.
-- SY, Marat
smime.p7s
Description: S/MIME Cryptographic Signature
