On Tue, 13 Mar 2012 10:02:16 + (UTC), jb wrote:
> Robert Bonomi mail.r-bonomi.com> writes:
>
> > ...
> > The fsck_ffs manpage says that 'lost+found' is _created_ *when*needed*,
> > in the root of a filesystem, if not already present.
> >
> > The presense of /mnt/lost+found is _not_ an erro
Robert Bonomi mail.r-bonomi.com> writes:
> ...
> The fsck_ffs manpage says that 'lost+found' is _created_ *when*needed*,
> in the root of a filesystem, if not already present.
>
> The presense of /mnt/lost+found is _not_ an error. just a surperfluous
> file that ended up there 'somehow'.
> ..
jb wrote:
>
> Hi,
>
> Each fs should have its own lost+found directory.
> It is used by fsck for placing recovered corrupted fs files in there.
> This implies the dir must have already existed (it may not be mounted ad hoc
> e.g. at boot time, during fs recovery).
>
> In FreeBSD 9, I found lost
On Tue, 13 Mar 2012 07:58:09 + (UTC), jb wrote:
> Hi,
>
> Each fs should have its own lost+found directory.
> It is used by fsck for placing recovered corrupted fs files in there.
Correct.
> This implies the dir must have already existed (it may not be mounted ad hoc
> e.g. at boot time, d
On Tue, Mar 13, 2012 at 2:58 AM, jb wrote:
> Hi,
>
> Each fs should have its own lost+found directory.
> It is used by fsck for placing recovered corrupted fs files in there.
> This implies the dir must have already existed (it may not be mounted ad
> hoc
> e.g. at boot time, during fs recovery).
Hi,
Each fs should have its own lost+found directory.
It is used by fsck for placing recovered corrupted fs files in there.
This implies the dir must have already existed (it may not be mounted ad hoc
e.g. at boot time, during fs recovery).
In FreeBSD 9, I found lost+found dir under /mnt.
This i
