This comes from Main HD is full. Home Assistant on Docker installation
After deleting /var/log/kern.log (which was about 8GB) I started monitoring it (tail) and nothing was written to it.
All I can see now is the following output to stdout (its a laptop):
EXT4-fs error (device sdb1): __ext4_find_entry:1531: inode #34340865: comm backup cleanup: reading directory lblock 0
df -i shows
Filesystem Inodes IUsed IFree IUse% Mounted on
udev 1745003 593 1744410 1% /dev
tmpfs 1760785 914 1759871 1% /run
/dev/sda1 5283840 5283840 0 100% /
tmpfs 1760785 225 1760560 1% /dev/shm
tmpfs 1760785 7 1760778 1% /run/lock
tmpfs 1760785 17 1760768 1% /sys/fs/cgroup
tmpfs 1760785 38 1760747 1% /run/user/1000
my first post here.
I am running 18.04.1 and I have recently gotten an error while booting - the screen remains black after POST and nothing happens. I went into recovery mode and found that my root partition doesn't get mounted due to orphaned inodes and the like - I cannot supply a log since I have rebooted twice since fixing that and I do not actually know how to access historical boot logs. I could fix it by running fsck.ext4 -p /dev/mapper/name-of-root-partition, and everything is fine and dandy again... However, I know this will probably happen again in the future, as I have had the exact same problem with Debian - it was in fact one of the reasons I switched to Ubuntu (the other being worse compatibility on Debian and some other small problems I didn't feel like fixing by hand, on Ubuntu it just werks).
Now fixing the problem is easy and rather pain-free, but I wonder what could be the reason, as it happens fairly frequently (I reckon twice a week) - I realized it might have something to do with me shutting the computer down with sudo shutdown now. Am I on the right track? I could not find any proper information about this approach being "dangerous" but at the same time everybody seems to be inputting various arguments before now, never running it "raw".
My hardware is pretty generic and I would assume rather unimportant, really. I have a single Kingston SSD and the weirdest thing in my setup is probably me forcing the kernel to load amdgpu instead of the default radeon drivers.
Are there any drawbacks to creating ext4 file systems with 2^32-1 inodes?
I have a 1tb drive and I would like to store 800 million to 1.5 billion small files on it. It seems that the max is 4 billion, so I'm wondering whether I could just set it to the max when creating an fs, or I should find some other solution.
How can I obtain list of items and their inode numbers in the current working directory ?