Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753574AbZIHFOK (ORCPT ); Tue, 8 Sep 2009 01:14:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753467AbZIHFOJ (ORCPT ); Tue, 8 Sep 2009 01:14:09 -0400 Received: from ns1.primeinteractive.net ([195.95.205.253]:53138 "EHLO mail.primeinteractive.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753376AbZIHFOI (ORCPT ); Tue, 8 Sep 2009 01:14:08 -0400 X-Greylist: delayed 463 seconds by postgrey-1.27 at vger.kernel.org; Tue, 08 Sep 2009 01:14:08 EDT Message-ID: <4AA5E5F3.30309@primeinteractive.net> Date: Tue, 08 Sep 2009 07:04:52 +0200 From: Pavol Cvengros User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3 MIME-Version: 1.0 To: linux-kernel@vger.kernel.org Subject: ext4+quota+nfs issue Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2757 Lines: 63 Hello, recently we have build and started to use raid storage with formatted capacity of 4.5T (ext4 formatted, default params). FS has quota turned on and is exported via NFS to nodes. If we turn qouta on on this FS and are trying to use it over NFS we get the following: ------------[ cut here ]------------ WARNING: at fs/quota/dquot.c:964 dquot_claim_space+0x181/0x190() Hardware name: S3210SH Modules linked in: nfs fscache nfsd lockd auth_rpcgss exportfs sunrpc coretemp hwmon ipmi_si ipmi_msghandler ehci_hcd sr_mod cdrom uhci_hcd floppy usbcore i2c_i801 i2c_core processor 3w_9xxx button thermal Pid: 268, comm: pdflush Tainted: G W 2.6.30-gentoo-r3_host #1 Call Trace: [] ? dquot_claim_space+0x181/0x190 [] ? warn_slowpath_common+0x89/0x100 [] ? dquot_claim_space+0x181/0x190 [] ? ext4_mb_mark_diskspace_used+0x423/0x440 [] ? ext4_mb_new_blocks+0x2cf/0x460 [] ? ext4_ext_find_extent+0x307/0x330 [] ? ext4_ext_get_blocks+0x578/0xfc0 [] ? __pagevec_free+0x48/0x70 [] ? blk_rq_bio_prep+0x35/0x130 [] ? ext4_get_blocks_wrap+0x210/0x380 [] ? mpage_da_map_blocks+0xe8/0x750 [] ? pagevec_lookup_tag+0x2e/0x50 [] ? write_cache_pages+0x11c/0x400 [] ? __mpage_da_writepage+0x0/0x190 [] ? ext4_da_writepages+0x329/0x4b0 [] ? do_writepages+0x32/0x70 [] ? __writeback_single_inode+0xb0/0x490 [] ? dequeue_entity+0x23/0x1c0 [] ? generic_sync_sb_inodes+0x316/0x4f0 [] ? writeback_inodes+0x5e/0x110 [] ? wb_kupdate+0xc6/0x160 [] ? pdflush+0x120/0x230 [] ? wb_kupdate+0x0/0x160 [] ? pdflush+0x0/0x230 [] ? kthread+0x64/0xc0 [] ? child_rip+0xa/0x20 [] ? kthread+0x0/0xc0 [] ? child_rip+0x0/0x20 ---[ end trace cb54e6523e9ab60d ]--- fstab entry: /dev/sdb1 /mnt/storage ext4 noatime,nodiratime,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0 qith quotaoff on tihs FS, warnings stop. Question is if it's safe to use quotas with this problem (warning) or not. Can't afford data damage. Thanks, Pavol Cvengros -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/