Timeline for What is the purpose of the lost+found folder in Linux and Unix?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 22, 2024 at 19:08 | comment | added | Daniel |
To those complaining of permission denied errors due to lost+found: I have a few external disks where I removed lost+found using sudo and then recreated it with $ mklost+found (without sudo). The permissions are now of my user and I get no permission denied errors using find.
|
|
| Dec 16, 2015 at 19:49 | comment | added | syntaxerror |
@JohanE You're telling me. However, the actual reason why I posted my comment was because this answer was trying to suggest us to "be thankful" for lost+found. This felt way too hilarious to be true (I sat here with a broad grin), for the ridiculously few times when we're thankful for it can't compete with those when we'd rather be able to cast a "Begone!" spell to this nuisant lo+fo thing.
|
|
| Dec 16, 2015 at 18:58 | comment | added | Trevor Boyd Smith |
@syntaxerror the reason I arrived at this question was precisely because I was doing a find operation and find kept generating a Permission denied warning. Given this question's answer, I know that lost+found is part of the filesystem and so I can safely ignore the generated warning (but I do wish it didn't produce the warning).
|
|
| Jun 22, 2014 at 0:24 | comment | added | Johan E | @syntaxerror: Good to hear you say that about the annoyances of find: `./lost+found': Permission denied. It bugs me from time to time too... | |
| S Feb 5, 2014 at 21:03 | history | suggested | erch | CC BY-SA 3.0 |
improved formatting
|
| Feb 5, 2014 at 20:52 | review | Suggested edits | |||
| S Feb 5, 2014 at 21:03 | |||||
| Sep 29, 2012 at 19:54 | comment | added | syntaxerror |
Valid point, however: these CAN become quite a nuisance anyway. For example, when trying to to a find operation on one or many ext[2|3|4] partition(s) from a non-admin user's account, you will always get these entirely unnecessary "permission denied" errors. Certainly, there are ways to circumvent those kinds of errors - but it's a bit awkward because the standard find . -name '*whatever*' won't do the trick.
|
|
| Aug 5, 2011 at 21:21 | history | answered | Arcege | CC BY-SA 3.0 |