On Wed, Apr 18, 2007 at 12:54:44AM -0600, Andreas Dilger wrote:
[ I'm quoting out of order here, and cc'ing the linux-ext4 list with
permission since I think the topics under discussion have a more
general interest. --Ted]
Just reading the updated e2fsck.conf.5 man page, and noticed
On Wed, 18 Apr 2007 15:54:00 +0200 Valerie Clement [EMAIL PROTECTED] wrote:
Running benchmark tests (FFSB) on an ext4 filesystem, I noticed a
performance degradation (about 15-20 percent) in sequential write tests
between 2.6.19-rc6 and 2.6.21-rc4 kernels.
I ran the same tests on ext3
On Wed, Mar 28, 2007 at 09:17:27 -0400,
John Anthony Kazos Jr. [EMAIL PROTECTED] wrote:
If you fsync() your data, you are guaranteed that also your data are
safely on disk when fsync returns. So what is the question here?
Pardon a newbie's intrusion, but I do know this isn't true. There is
On Apr 16, 2007 18:01 +1000, Timothy Shimmin wrote:
--On 12 April 2007 5:05:50 AM -0600 Andreas Dilger [EMAIL PROTECTED]
wrote:
struct fiemap_extent {
__u64 fe_start; /* starting offset in bytes */
__u64 fe_len; /* length in bytes */
}
struct
On Apr 16, 2007 21:22 +1000, David Chinner wrote:
On Thu, Apr 12, 2007 at 05:05:50AM -0600, Andreas Dilger wrote:
struct fiemap_extent {
__u64 fe_start; /* starting offset in bytes */
__u64 fe_len; /* length in bytes */
}
struct fiemap {
