Hi Frank, * Frank Guthausen <fg.deb...@shimps.de> [2024-12-11; 12:21 +01]: > On Wed, 11 Dec 2024 12:01:30 +0100 > Gregor Zattler <telegr...@gmx.net> wrote: >> >> Any ideas, pointers? > > Please check free space and available inodes: > > df -h > df -hi
not via df, but this information: 0 (master *) grfz@no:~$ sudo tune2fs -l /dev/mapper/mic-backup tune2fs 1.47.0 (5-Feb-2023) Filesystem volume name: mic-backupfs Last mounted on: /mnt/mic-backup Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index sparse_super2 filetype needs_recovery extent 64bit mmp flex_bg large_dir sparse_super large_file huge_file dir_nlink extra_isize metadata_csum Filesystem flags: signed_directory_hash Default mount options: user_xattr acl Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 960430080 Block count: 960427008 Reserved block count: 48021350 Overhead clusters: 60352093 Free blocks: 256205203 Free inodes: 871021955 So the problem is not on the file system level but with one directory. > Check mount state: > > mount > > You might try to mount the file system read-only and copy or rsync the > data from this state. The target file system should provide enough free > space for the data, too. Sadly not possible, does not stat the files in the directory. Thanks. Ciao; Gregor -- -... --- .-. . -.. ..--.. ...-.-
