Felix Miata wrote:
The last 3 recordings, all made after deleting the multiplicity of test recordings, and bringing freespace back to 96%, have completed normally, so I seem to be back to trying to figure out exactly how much space can actually be used. Many times on Linux PCs I've found it possible to get df to show 0% free on / without the system locking up, at least, before systemd and journald usurped predictable, tried and true.
On a data disk, not used by the OS, you can (at least on 'xfs', get it to 0 as root...er... hmm...ok, not exactly:
sudo lvcreate -C y -L 1G -n FillMe /dev/Data sudo ./mkfs-xfs-raid with_data /dev/Data/FillMe cmd = mkfs.xfs -i projid32bit=0 -d su=64k,sw=4 -s size=4096 -L with_data -f /dev/Data/FillMe
meta-data=/dev/Data/FillMe isize=256 agcount=8, agsize=32752 blks = sectsz=4096 attr=2, projid32bit=0 = crc=0 finobt=0 data = bsize=4096 blocks=262016, imaxpct=25 = sunit=16 swidth=64 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=0 log =internal log bsize=4096 blocks=1605, version=2 = sectsz=4096 sunit=1 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0
sudo mkdir /mnt/fillme sudo mount /dev/Data/FillMe /mnt/fillme/ -t xfs -o defaults,nodiratime,swalloc,largeio,logbsize=256k,barrier sudo chown -R law.law /mnt/fillme df /mnt/fillme Filesystem Size Used Avail Use% Mounted on /dev/mapper/Data-FillMe 1018M 33M 985M 4% /mnt/fillme
\df /mnt/fillme Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/Data-FillMe 1041644 33152 1008492 4% /mnt/fillme
\df -B 4096 /mnt/fillme Filesystem 4K-blocks Used Available Use% Mounted on /dev/mapper/Data-FillMe 260411 8288 252123 4% /mnt/fillme
xfs_mkfile -p 1008476k x \df -h . Filesystem Size Used Avail Use% Mounted on /dev/mapper/Data-FillMe 1018M 1018M 16K 100% /mnt/fillme
--- The closest I could come to a full disk was 16K short. Oh well... 16K out of 1G, I am guessing, but might also get all by 16K out of 1T as well... But NOTE: If I allocated lots of little 4K files, I wouldn't get close to that amount, since each file needs at least 1 block to hold its space pointers:
rm x df -k . Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/Data-FillMe 1041644 33152 1008492 4% /mnt/fillme echo -n 1 >x df -k . Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/Data-FillMe 1041644 33176 1008468 4% /mnt/fillme ll -hs x 4.0K -rw-rw-r-- 1 1 Mar 15 13:03 x
---- The indirect blocks don't appear to be part of it's size to "du" or "ls", but they still get allocated out of "df"'s figure. Note, even 'root' can't allocate that final 4K space(tried)... But it looks like to allocate the entire 1G, it only took 1block of overhead (I'm assuming the above block table could be held in 1 block, though I might be wrong...?) L8r -l -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org