Tag Info

New answers tagged

0

According to Essential System Administration Disk errors or incorrect system shutdown may cause files to become lost: lost files refer to disk locations that are marked as in use in the data structures on the disk, but that are not listed in any directory (e.g., a non-empty in ode that isn't listed in any directory). When the system is booting, it runs a ...


2

"The lost+found directory already exists in / on every distro I've checked." But that's not the point. Every "real" filesystem (which maps to a block storage of some sort, as opposed to pseudo filesystems like /proc and swap) needs a lost+found orphanage. For example, if you have a separate filesystem for /home, then there should be /home/lost+found. ...


8

Why would you ever need to run this command? In case the lost+found directory doesn't exist. Since it's just an ordinary directory, the root user can remove it using rm -r. Some versions of fsck, when they need to make use of a lost+found directory, will create it if it doesn't exist, and some versions won't. If there's no lost+found directory, fsck ...


3

Q1. Why would you ever need to run this command? The lost+found directory already exists in / on every distro I've checked. Something needs to create the lost+found, this command would appear to do that. Every medium you mount needs to maintain its own lost+found. excerpt from man page mklost+found is used to create a lost+found directory in the ...



Top 50 recent answers are included