search for: hsx

...Size Used Avail Use% Mounted on /dev/mapper/vg_server-lv_root 26G 24G 869M 97% / tmpfs 2.0G 0 2.0G 0% /dev/shm /dev/sda1 477M 80M 373M 18% /boot And then I've tried to find the conflictive files by running: *du -hsx * | sort -rh | head -10* du: cannot access `proc/3662/task/3662/fd/4': No such file or directory du: cannot access `proc/3662/task/3662/fdinfo/4': No such file or directory du: cannot access `proc/3662/fd/4': No such file or directory du: cannot access `proc/3662/fdinfo/4': No such...

...> Filesystem Size Used Avail Use% Mounted on > /dev/mapper/vg_server-lv_root 26G 24G 869M 97% / Linux boxes typically reserve the last 5% of volume space for use by root only, so as far as your normal user is concerned, the volume is in fact full. > *du -hsx * | sort -rh | head -10* > du: cannot access `proc/3662/task/3662/fd/4': No such file or directory > du: cannot access `proc/3662/task/3662/fdinfo/4': No such file or directory > du: cannot access `proc/3662/fd/4': No such file or directory > du: cannot access `proc/3662/fdi...

...em show''. Since the mount flag is at mount time only, degraded seems to mean "be degraded if needed" instead of a positive indicator that the volume is indeed degraded" $ mount | grep btrfs /dev/sdc on /mnt/new-store type btrfs (rw,relatime,degraded,space_cache) $ du -hsx /mnt/new-store 305G /mnt/new-store $ df -h | grep new-store /dev/sdc 932G 307G 160G 66% /mnt/new-store $ btrfs fi show /dev/sdc Label: ''new-store'' uuid: 14e6e9c7-b249-40ff-8be1-78fc8b26b53d Total devices 2 FS bytes used 540.00KB devid 2 size 465...