June 24, 200917 yr At least I don't think this is a user share issue... The web UI and the du command say that I have 25G on disk4: root@storage:/mnt# df -h Filesystem Size Used Avail Use% Mounted on /dev/sdg1 495M 48M 448M 10% /boot /dev/md4 466G 442G 25G 95% /mnt/disk4 /dev/md3 233G 229G 4.9G 98% /mnt/disk3 /dev/md5 373G 348G 25G 94% /mnt/disk5 /dev/md2 280G 272G 7.7G 98% /mnt/disk2 /dev/md6 466G 429G 37G 93% /mnt/disk6 /dev/md1 280G 272G 7.9G 98% /mnt/disk1 shfs 2.1T 2.0T 107G 95% /mnt/user But when I try to copy a 730 MB file I get an out of space error: root@storage:/mnt# mv disk3/Media/TV\ Shows/TV\ Shows/Foo/Season\ 6/big_file.avi disk4/Media/TV\ Shows/TV\ Shows/Foo/Season\ 6/ mv: writing `disk4/Media/TV Shows/TV Shows/Foo/Season 6/big_file.avi': No space left on device I get an out of space error if I try the same move in windows explorer from disk3 to disk4. Does anyone know what's going on?
June 24, 200917 yr Does anyone know what's going on? No, but I would start by running reiserfsck over the drive in question.
June 24, 200917 yr are you sure you did not create a "sparse file" (one whose size is much larger than the actual number of blocks used) See: http://en.wikipedia.org/wiki/Sparse_file The name of your file "big_file.avi" leads me to think it is not a movie. Type the following two commands to see the actual size of the file in bytes, and the apparent size in bytes: du -s -B1 --apparent-size /mnt/disk3/Media/TV\ Shows/TV\ Shows/Foo/Season\ 6/big_file.avi and du -s -B1 /mnt/disk3/Media/TV\ Shows/TV\ Shows/Foo/Season\ 6/big_file.avi If big_file.avi is larger than the available free space on your disk4, you would get the error you saw, even if it only occupied a few blocks of space originally, since "mv"would try to fill in all the (zero value) blocks originally not allocated on the disk. Joe L.
June 24, 200917 yr Author Joe, it's probably not a sparse file issue since this is a media server, it really is a movie, and I create my files from the Windows side. It looks like my disk has errors... reiserfsck is going to take over an hour since it said I have to rebuild the trees. Hopefully that will fix the problem. Hopefully after fixing the errors things will make more sense. Thanks!
June 24, 200917 yr Joe, it's probably not a sparse file issue since this is a media server, it really is a movie, and I create my files from the Windows side. It looks like my disk has errors... reiserfsck is going to take over an hour since it said I have to rebuild the trees. Hopefully that will fix the problem. Hopefully after fixing the errors things will make more sense. Thanks! That would explain everything... Your use of "big_file.avi" in your example threw me off track. I'm sure that you'll be much better once the file-system errors are resolved. Joe L.
June 25, 200917 yr Author Weird. After reiserfsck, disk4 is at 100%, not 95%: root@storage:~# df -h Filesystem Size Used Avail Use% Mounted on /dev/sdg1 495M 48M 448M 10% /boot /dev/md3 233G 229G 4.9G 98% /mnt/disk3 /dev/md4 466G 466G 693M 100% /mnt/disk4 /dev/md1 280G 254G 26G 91% /mnt/disk1 /dev/md2 280G 272G 7.7G 98% /mnt/disk2 /dev/md5 373G 348G 25G 94% /mnt/disk5 /dev/md6 466G 429G 37G 93% /mnt/disk6 shfs 2.1T 2.0T 101G 96% /mnt/user
June 25, 200917 yr Weird. After reiserfsck, disk4 is at 100%, not 95%: root@storage:~# df -h Filesystem Size Used Avail Use% Mounted on /dev/sdg1 495M 48M 448M 10% /boot /dev/md3 233G 229G 4.9G 98% /mnt/disk3 /dev/md4 466G 466G 693M 100% /mnt/disk4 /dev/md1 280G 254G 26G 91% /mnt/disk1 /dev/md2 280G 272G 7.7G 98% /mnt/disk2 /dev/md5 373G 348G 25G 94% /mnt/disk5 /dev/md6 466G 429G 37G 93% /mnt/disk6 shfs 2.1T 2.0T 101G 96% /mnt/user Perhaps it created a lost+found directory and placed a few files there? Or perhaps it is why you were running out of space... since you really only had 692meg free on it. Glad the file-system check worked its magic.
June 25, 200917 yr Weird. After reiserfsck, disk4 is at 100%, not 95%Well that would certainly explain why you couldn't add much to it. As Joe implies, the check presumably found and re-linked some orphaned file blocks. If it could figure out where they came from then it should have linked them back to their original locations, but it's more likely that you will find a bunch of fragments in /lost+found. If so, and you can't figure out where they came from either, just delete them to reclaim the free space you thought you had.
Archived
This topic is now archived and is closed to further replies.