Hi,

On 2012-01-12 09:31, Andrew Chittenden wrote:
> Since installing autofs5, all active automounts have been complained
> about. For example, when /home/andyc and /var/chroot/ia32/home/andyc
> have been automounted:
> 
> /etc/cron.daily/standard:
> 
> Some local file systems lack a lost+found directory. This means if the
> file system is damaged and needs to be repaired, fsck will not have
> anywhere to put stray files for recovery. You should consider creating
> a lost+found directory with mklost+found(8).
> 
> The following lost+found directories were not available:
> 
> /home/andyc/lost+found
> /var/chroot/ia32/home/andyc/lost+found

If those are ext{2,3,4} filesystems, the script is working as expected,
ie those filesystems are missing the lost+found directory. You can
disable this check in /etc/default/cron.

If those are bind mounts*), the issue here is that /etc/mtab recently
became a symlink to /proc/mounts, which doesn't store information about
bind mounts. Effectively, this means that we will probably have to drop
this script from Wheezy altogether. (It would have been moved out of the
cron package anyway)

Christian


*) I'm not sure if automount can do this, just speculating here

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to