>> drwxr-xr-x 2 root root 12288 May 4 21:35 lost+found
>> drwxr-xr-x 5 root root 1024 May 5 12:12 mnt
>> dr-xr-xr-x 33 root root 0 Jun 23 19:06 proc
>> "lost+found"
>> drwxr-xr-x 2 root root 12288 May 4 21:35 .
>> drwxr-xr-x 17 root root 1024 May 28 16:40 ..
>> If the present scheme allocates 13 * 1024 bytes for just "." and
>> "..", I feel it is time to rethink the directory handling.
> Nono, lost+found is /deliberately/ 12K.
Actually, it isn't - it is deliberately 12 BLOCKS. True, this is 12k
on a 1k block filesystem, but it is 48k on a 4k block filesystem. I'm
not sure whether this was intentional or a bug in the mklost+found
code.
> The reason is that you can't (easely) enlarge a directory on a
> disk which is beeing recovered. By making lost+found at least
> 12K we have enough room for making names for lost files
That's basically what I assumed was the reason.
Best wishes from Riley.
+----------------------------------------------------------------------+
| There is something frustrating about the quality and speed of Linux |
| development, ie., the quality is too high and the speed is too high, |
| in other words, I can implement this XXXX feature, but I bet someone |
| else has already done so and is just about to release their patch. |
+----------------------------------------------------------------------+
* ftp://ftp.MemAlpha.cx/pub/rhw/Linux
* http://www.MemAlpha.cx/kernel.versions.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/