2008-July Archive by Thread
Messages are ordered newest-to-oldest in this index. The newest
threads will be at the top of this page, the oldest will be at the bottom.
Within a single thread, the first mail note is the START of the
thread; the notes following that are in the chronological order of
when they were received. So globally, newest messages are at the top,
but within a thread, the oldest (the start of the thread) is at the
top.
If you think about it, it is confusing. Just go with the flow and everything will be all right.
- non-contiguous Inodes,
John Nelson
- File permission getting read only,
Swapana Ghosh
- e2fsck message "inode is too big",
thorsten . henrici
- ext3 filesystem --> read-only,
Balu manyam
- debugfs question: What does "expand" do?,
Charles Riley
- fsck.ext3 questions,
Charles Riley
- ext3 filesystem becomes read-only,
Eli Dorfman
- What used to be a directory is now a 0 length file - recovery possible?,
Charles Riley
- sharp increase in 'used' blocks after plain fs copy,
Victoria Muntean
- aborted journal and kernel bug on RHEL AP 5.1 on SUN AMD 64bit (X4200M2),
Rossoni Fabio
- Re: indexing symbolic links,
Levent Serinol
- Ext3 problem,
Iskandar Prins
- Nanosecond date resolution,
Pau Garcia i Quiles
- max fs size with 1k blocks,
Jure Pečar
- Re: debugfs question,
Andreas Dilger