@ColinTheMathmo@dougmerritt You can manually specify the number of inodes on a device when creating the filesystem on the USB disk using the -N option to mke2fs - a bit desperate
Do we know the cd command didn't silently fail?
(i.e., are you in the directory you think you are? There might also be some special treatment for // that differs between commands. These are not URLs.)
(admittedly it's been a couple decades since I last had that kind of fail -- these are more NFS-ish kinds of problems)
(0) we can rebuild the inode table without having to mess with the rest of the disk
(1) we need to reformat the disk (copy everything out and back)
(2) we need to recompile the kernel to allow bigger inode values
(3) we're fucked because inode_t is int32 and we have more than 4 billion files in the same filesystem
We can format the disk with a larger number of inodes, but it's a reformat. Currently the number of available inodes is 152616960, and my disk is 40% full. So if I reformat with 3 times as many inodes, rounded up to 500M, then I should be OK.
@wrog Thought that doesn't work, because with each new backup I use as many inodes as I have files, but don't use anything like that space, because anything that hasn't changed is hard-lunk to the previous backup.
I need to work on this.
But for now, I'll delete some of the old backups that I really don't need.
@ColinTheMathmo could it be one of those dubious USB devices that reports itself as far bigger than it actually is? (Example: A friend once gave me a 1 Tb USB key she'd bought in Shanghai. It did not really have 1 Tb of storage)
Add comment