| 1 |
On Tuesday 14 February 2006 18:55, Richard Fish wrote: |
| 2 |
> On 2/14/06, Peter Humphrey <prh@××××××××××.uk> wrote: |
| 3 |
> > I did that some time ago in a simple-minded fashion, but I've had to |
| 4 |
> > revise my layout somewhat. I had an ext3 partition solely for |
| 5 |
> > /usr/portage, and it was mounted on that node, but every emerge |
| 6 |
> > --sync deleted the /lost+found directory. I don't know how serious |
| 7 |
> > that is, but of course no-one likes to |
| 8 |
> |
| 9 |
> Losing lost+found on an ext3 filesystem is pretty harmless. It is the |
| 10 |
> directory where fsck will attach files that still exist but were |
| 11 |
> detached from the directory tree (i.e, 'lost'). Since this should |
| 12 |
> *never* happen with ext3, there doesn't seem to be any point in |
| 13 |
> lost+found. |
| 14 |
> |
| 15 |
> The one exception would be if you sometimes mount the filesystem as |
| 16 |
> ext2. |
| 17 |
|
| 18 |
And even then, the only thing that happens is that those files which where |
| 19 |
reattached there are now deleted. As finding what file it actually is is |
| 20 |
hard, and in the case of a /usr/portage partition/disk also pointless, |
| 21 |
there is no harm whatsoever in losing this directory with a sync. |
| 22 |
Removing it does certainly not influence filesystem integrity. |
| 23 |
|
| 24 |
Paul |
| 25 |
|
| 26 |
-- |
| 27 |
Paul de Vrieze |
| 28 |
Gentoo Developer |
| 29 |
Mail: pauldv@g.o |
| 30 |
Homepage: http://www.devrieze.net |
Archives