OK to delete/rename lost+found on disk?

[rikona]

Hello Nils,

Wednesday, March 11, 2015, 11:29:59 PM, Nils wrote:

> rikona wrote:
>> Is it OK to delete/rename/change permissions for lost+found on disk
>> [assuming I can - owned by root]? Opinions on the net range from 'OK'
>> to 'h*ll no'.

> Take this as just another opinion from the internet:

I have a great deal of respect for your opinion, and for others on
this list. In that sense, it is not just another opinion.

> Yes, you can delete lost+found as root. If you run e2fsck on the
> partition afterwards, it would recreate lost+found if it doesn't
> exist. Therefore it would only help, if you never run e2fsck.

Thanks for the info. I was thinking that it might be better to just
change permissions, which would also remove the permission/backup
problem. Would that be better? Any problem with e2fsck, or security,
if I allow everyone full access?

Needing to do a backup, I found a somewhat hokey workaround - I added
an 'all' folder, put everything in there, and backed up 'all' instead
of the disk. This DOES back up everything OK, and I was able to do a
successful backup with grsync. Interesting side effect - also
simplifies mapping disks for Windows - just map 'all'.

>> It looks as though 'permission denied' for this is what is causing
>> my backups not to work correctly [was described in an earlier
>> email]. If I can safely get rid of lost+found then perhaps grsync
>> backups might start working properly...

> Maybe you should change your backup script to exclude lost+found.

I've been using grsync, not a script - no mention of exclude so I was
not aware of that. I do see it in the rsync docs though. Grsync shows
the CL that is actually used - maybe I'll start with that and just add
an exclude, for starters. Rsync has a lot of options I need to learn
about... :-)

Thanks for the help.

-- 

 rikona