2006-November 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.
- Best Practices for Data Recovery for corrupted EXT2/3?,
Thomas Weeks
- how to prevent filesystem check,
Sebastian Reitenbach
- ext3 4TB fs limit on amd64 (FAQ?),
Ralf Gross
- Re: how does ext3 handle no communication to storage,
Coywolf Qi Hunt
- BUG: warning at kernel/softirq.c:141,
Christian Kujau
- 2.6.19-rc5-git4 benchmarks,
Christian Kujau
- ext3 4TB FS limit (FAQ),
Ralf Gross
- Online filesystem check,
Oliver Hookins
- ext3 corrupted,
Bogdan Scintee
- Ext3 - which blocksize for small files?,
witscher
- How to create a huge file system - 3-4TB?,
Raghu Ni
- Re: e2defrag - Unable to allocate buffer for inode priorities,
Andreas Dilger
- compressed read-only ext3 file system,
Keld Jørn Simonsen
- question about exact behaviour with data=ordered.,
Neil Brown
- RHEL connundrum with df and du,
Simon Alman
- e2fsck: Bad magic number in super-block,
M. Lewis