Ext4 & Quota not working?

Discussion in 'Installation/Configuration' started by bswinnerton, Mar 9, 2010.

  1. bswinnerton

    bswinnerton New Member

    My syslogs are filling up by the second, I'm getting the following kernel messages over and over:


    Code:
    Mar  9 15:34:50 cw-ws kernel: [69005.223998] ------------[ cut here ]------------
    Mar  9 15:34:50 cw-ws kernel: [69005.223998] WARNING: at /build/buildd/linux-2.6.31/fs/quota/dquot.c:964 dquot_claim_space+0x84/0x130()
    Mar  9 15:34:50 cw-ws kernel: [69005.223998] Hardware name: VMware Virtual Platform
    Mar  9 15:34:50 cw-ws kernel: [69005.223998] Modules linked in: xt_multiport quota_v2 quota_tree iptable_filter ip_tables x_tables ppdev parport_pc lp shpchp psmouse parport intel_agp serio_raw agpgart i2c_piix4 floppy pcnet32 mii mptspi mptscsih mptbase scsi_transport_spi
    Mar  9 15:34:50 cw-ws kernel: [69005.223998] Pid: 32, comm: pdflush Tainted: G        W  2.6.31-20-generic-pae #57-Ubuntu
    Mar  9 15:34:50 cw-ws kernel: [69005.223998] Call Trace:
    Mar  9 15:34:50 cw-ws kernel: [69005.223998]  [<c014692d>] warn_slowpath_common+0x6d/0xa0
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c02298f4>] ? dquot_claim_space+0x84/0x130
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c02298f4>] ? dquot_claim_space+0x84/0x130
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c0146975>] warn_slowpath_null+0x15/0x20
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c02298f4>] dquot_claim_space+0x84/0x130
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c029154f>] ext4_mb_mark_diskspace_used+0x33f/0x390
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c028bb32>] ? ext4_mb_use_preallocated+0x232/0x240
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c028bf42>] ? ext4_mb_initialize_context+0x82/0x290
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c0292f3e>] ext4_mb_new_blocks+0x2fe/0x580
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c0287a7f>] ? ext4_ext_find_extent+0xff/0x280
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c0289b15>] ext4_ext_get_blocks+0x415/0x5a0
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c026a9ef>] ext4_get_blocks+0x23f/0x2c0
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c026b074>] mpage_da_map_blocks+0x94/0x400
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c02a0473>] ? jbd2_journal_start+0x93/0xd0
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c026b64c>] ext4_da_writepages+0x26c/0x520
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c01bb240>] ? __writepage+0x0/0x30
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c01bc511>] do_writepages+0x21/0x40
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c02074ee>] writeback_single_inode+0x16e/0x3d0
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c013cdb4>] ? dequeue_entity+0x14/0x290
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c045c1d4>] ? dm_any_congested+0x54/0x70
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c0207bed>] generic_sync_sb_inodes+0x38d/0x4a0
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c0207ddd>] writeback_inodes+0x4d/0xe0
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c01bb402>] wb_kupdate+0xa2/0x110
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c01bcbe7>] __pdflush+0xf7/0x1f0
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c01bcce0>] ? pdflush+0x0/0x40
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c01bcce0>] ? pdflush+0x0/0x40
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c01bcd19>] pdflush+0x39/0x40
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c01bb360>] ? wb_kupdate+0x0/0x110
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c015dd9c>] kthread+0x7c/0x90
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c015dd20>] ? kthread+0x0/0x90
    Mar  9 15:34:50 cw-ws kernel: [69005.223999]  [<c0104047>] kernel_thread_helper+0x7/0x10
    Mar  9 15:34:50 cw-ws kernel: [69005.223999] ---[ end trace f1b5ca139e0703df ]---
    

    Here are the outputs of mount:
    Code:
    /dev/mapper/cw--ts-root on / type ext4 (rw,errors=remount-ro,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0)
    proc on /proc type proc (rw)
    none on /sys type sysfs (rw,noexec,nosuid,nodev)
    none on /sys/fs/fuse/connections type fusectl (rw)
    none on /sys/kernel/debug type debugfs (rw)
    none on /sys/kernel/security type securityfs (rw)
    udev on /dev type tmpfs (rw,mode=0755)
    none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
    none on /dev/shm type tmpfs (rw,nosuid,nodev)
    none on /var/run type tmpfs (rw,nosuid,mode=0755)
    none on /var/lock type tmpfs (rw,noexec,nosuid,nodev)
    none on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
    /dev/sda5 on /boot type ext2 (rw)
    df -h:
    Code:
    Filesystem            Size  Used Avail Use% Mounted on
    /dev/mapper/cw--ts-root
                          9.2G  2.4G  6.3G  28% /
    udev                  502M  152K  502M   1% /dev
    none                  502M     0  502M   0% /dev/shm
    none                  502M  132K  502M   1% /var/run
    none                  502M     0  502M   0% /var/lock
    none                  502M     0  502M   0% /lib/init/rw
    /dev/sda5             228M   27M  189M  13% /boot
    root@cw-ws:~# 
    
    and fdisk -l
    Code:
    
    Disk /dev/sda: 42.9 GB, 42949672960 bytes
    255 heads, 63 sectors/track, 5221 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x000ee752
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sda1   *           1        1274    10233373+  8e  Linux LVM
    /dev/sda2            1275        1305      249007+   5  Extended
    /dev/sda5            1275        1305      248976   83  Linux
    
     
  2. bswinnerton

    bswinnerton New Member

    ..oh and fstab:

    Code:
    # /etc/fstab: static file system information.
    #
    # Use 'blkid -o value -s UUID' to print the universally unique identifier
    # for a device; this may be used with UUID= as a more robust way to name
    # devices that works even if disks are added and removed. See fstab(5).
    #
    # <file system> <mount point>   <type>  <options>       <dump>  <pass>
    proc            /proc           proc    defaults        0       0
    /dev/mapper/cw--ts-root /               ext4    errors=remount-ro,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0 0       1
    # /boot was on /dev/sda5 during installation
    UUID=8f5d3c11-ac72-4321-8a31-6a6571edce8e /boot           ext2    defaults        0       2
    /dev/mapper/cw--ts-swap_1 none            swap    sw              0       0
    /dev/scd0       /media/cdrom0   udf,iso9660 user,noauto,exec,utf8 0       0
    /dev/fd0        /media/floppy0  auto    rw,user,noauto,exec,utf8 0       0
    
    I'm confused as to why my hard drive is being mounted on /dev/mapper/cw--ts-root

    The actual name of the server is cw-ws. I had to change the hostname after my installation from cw-ts to cw-ws because of a typo. Could this be causing any of the problems? Any insight is greatly appreciated.
     
  3. Doug G

    Doug G Member HowtoForge Supporter

    I'm guessing there is some bug with quota and new kernels, I get similar syslog errors on a Fedora 12/ispconfig3 setup. Since I don't need quota in my environment I just turned quota off by changing fstab. I'm using 2.6.31 kernel btw.

    Your fstab mount point sounds like you're mounting on a lvm volume.
     
  4. bswinnerton

    bswinnerton New Member

    Hmm, my knowledge with kernels is extremely little. About all I know is the
    Code:
    uname -r
    code.

    I've disabled quota just for the sake of disk space. Is there anything that you recommend to troubleshoot the problem? I don't even know where to begin. I've heard of compiling your own kernels, but wouldn't have the slightest clue how if that were to help my problem.
     
  5. falko

    falko Super Moderator Howtoforge Staff

    Unfortunately I don't know if building a new kernel helps... :(
     
  6. bswinnerton

    bswinnerton New Member

    :( Should I just keep quota disabled?
     
  7. falko

    falko Super Moderator Howtoforge Staff

    If you don't need it, you can disable it.
     
  8. bswinnerton

    bswinnerton New Member

    Okay, I'm not sure what fixed it but I just updated to linux-image-2.6.31-20-generic-pae via apt-get update/upgrade and also changed my /etc/fstab to remove an extra 0 that I found after the options.

    Re-enabled Quota and everything seems to be fine ::fingers crossed::
     
  9. t.roijers

    t.roijers Member

    Quota problems

    Hi,

    I'm also using the 2.6.31-20-generic-pae kernel.
    wich 0 needs to be removed from my fstab below?

    UUID=235160e2-d150-4e75-996c-68207a4c40f6 / ext4 errors=remount-ro,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0 0 1


    Thanx,
    Tim

     
  10. bswinnerton

    bswinnerton New Member

    @t.roijers, your /etc/fstab looks fine to me.

    I'm still battling this problem. I just used apt-get and there was a new kernel update, so I turned quota back on.

    Besides obviously checking for these same sort of errors in the error log, is there a way to check if quota is actually working?
     
  11. lewis_saint

    lewis_saint New Member

    Any news on this?
     
  12. falko

    falko Super Moderator Howtoforge Staff

    Are you having the same problem?
     
  13. lewis_saint

    lewis_saint New Member

    I had a Debian Squeeze box with ext4/quotas up for 200 days, then went down last week. The syslog was filled with the exact error at the beginning of the thread. Perhaps a kernel issue? I believe I had 2.6.32-4 or similar.

    Lewis
     

Share This Page