the point is: there is NOT such a directory in the file system!
So why this happen and how I can fix the problem?
As I said, there is NO lost and found directory and the layout of this disk is this one:
So, as you can see, there is space on / to eventually create lost+found.
It as to be said that, even if the disk si marked dirty, it boot and it works fine. Then I don't know how safe it could be to work on a system presenting this behaviour.
What can I do? And if I do clone the disk on a new one, could still have this problem?
How fix it?
So why this happen and how I can fix the problem?
Code:
UNREF DIR I=451508 OWMNER=root MODE=40755
SIZE=2560 MTIME=May 16 18:45 2018
RECONNECT? yes
SORRY. NO SPACE in lost+found DIRECTORY
UNEXPECTED SOFT UPDATE INCONSISTENCY
Code:
Filesystem Size Used Avail Capacity Mounted on
/dev/da0s1a 496M 204M 252M 45% /
devfs 1,0K 1,0K 0B 100% /dev
/dev/da0s1e 1,9G 704K 1,8G 0% /tmp
/dev/da0s1f 34G 24G 7,8G 75% /usr
/dev/da0s1d 2,9G 2,0G 670M 76% /var
procfs 4,0K 4,0K 0B 100% /proc
linprocfs 4,0K 4,0K 0B 100% /usr/compat/linux/proc
fdescfs 1,0K 1,0K 0B 100% /dev/fd
It as to be said that, even if the disk si marked dirty, it boot and it works fine. Then I don't know how safe it could be to work on a system presenting this behaviour.
What can I do? And if I do clone the disk on a new one, could still have this problem?
How fix it?