Home » Mailing list archives » linux-ext4 » 2010 » October

linux-ext4 mailing list

FromSubjectsort iconDate
Lukas Czerner
[PATCH] e2fsck: Discard free data and inode blocks.
In Pass 5 when we are checking block and inode bitmaps we have great opportunity to discard free space and unused inodes on the device, because bitmaps has just been verified as valid. This commit takes advantage of this opportunity and discards both, all free space and unused inodes. I have added new option '-K' which when set, disables discard. Also when the underlying device does not support discard, or BLKDISCARD ioctl returns any kind of error, or when some errors occurred in bitmaps, ...
[ message continues ]
Oct 11, 3:37 am 2010
Jan Kara
Re: ext4: do not get s_umount sem on ext4_quota_off
The patch is OK, but Ted usually merges ext4 patches (even quota related, unless they are dependent on other generic quota stuff). -- Jan Kara <jack@suse.cz> SUSE Labs, CR --
[ message continues ]
Oct 11, 6:37 am 2010
Andrew Morton
Re: [PATCH RFC 0/3] Block reservation for ext3
On Mon, 11 Oct 2010 16:28:13 +0200 I thought we'd actually fixed this. I guess we didn't. I think what we did do was to ensure that a subsequent fsync()/msync() would reliably report the data loss (has anyone tested this in the past few Yes, people do this. With a 64-bit address space they create a gargantuan mmap of the entire database and just populate teeny bits of it simply with CPU stores. They'd be unhappy if the kernel started ouch. When I did ext2 delayed allocation back ...
[ message continues ]
Oct 11, 2:59 pm 2010
Jan Kara
Re: [PATCH RFC 0/3] Block reservation for ext3
Yeah, I understand that and I've been also thinking for some time whether I cannot avoid implementing block reservation but I haven't come up with anything really acceptable. Moreover, unless we write via mmap to a sparse file, the code paths taken are changed only a little (only when and how Well, mmap beyond EOF is still undefined AFAIK (although Linux traditionally supports it) but mmap of sparse files was always supposed to work. My favorite user of sparse-file mmap is Berkeley DB, some ...
[ message continues ]
Oct 11, 7:28 am 2010
Jan Kara
Re: ext3/jbd: Avoid WARN() messages when failing to writ ...
Yup. Done. Thanks. Honza -- Jan Kara <jack@suse.cz> SUSE Labs, CR --
[ message continues ]
Oct 11, 8:17 am 2010
Theodore Tso
Re: ext3/jbd: Avoid WARN() messages when failing to writ ...
I could have sworn that I had fixed this for both ext3 and ext4. I guess i didn't track to make sure the ext3 version of the patch made it into mainline. Thanks, Darrick for fixing this! -- Ted --
[ message continues ]
Oct 11, 9:42 am 2010
Eric Sandeen
Re: ext3/jbd: Avoid WARN() messages when failing to writ ...
Probably worth mentioning the ext4 version is: commit 914258bf2cb22bf4336a1b1d90c551b4b11ca5aa Author: Theodore Ts'o <tytso@mit.edu> Date: Mon Oct 6 21:35:40 2008 -0400 ext4/jbd2: Avoid WARN() messages when failing to write to the superblock This fixes some very common warnings reported by kerneloops.org Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> --
[ message continues ]
Oct 11, 8:05 am 2010
Lukas Czerner
Re: [PATCH 0/4 v. 9] Ext3/Ext4 Batched discard support
Hi Ted, I was wondering, is there still anything holding this patch-set from being merged in ? Thanks! -Lukas --
[ message continues ]
Oct 11, 10:02 am 2010
Andreas Dilger
Re: [Bug 17361] Watchdog detected hard LOCKUP in jbd2_jo ...
In my experience, this is typically caused by stack overflow smashing the task struct and randomly setting preempt_count to a non-zero value. Cheers, Andreas --
[ message continues ]
Oct 11, 1:43 pm 2010
Andreas Dilger
Re: [PATCH] Skip "rootfs" entry when checking for ext4 f ...
--
[ message continues ]
Oct 11, 1:59 pm 2010
previous daytodaynext day
October 10, 2010October 11, 2010October 12, 2010