xfs
[Top] [All Lists]

Re: weird quota issue

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: weird quota issue
From: "Weber, Charles (NIH/NIA/IRP) [C]" <weberc@xxxxxxxxxxxxxxx>
Date: Tue, 23 Dec 2014 13:48:22 -0500
Cc: "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20141223024248.GC4521@dastard>
References: <3BD1EE39-8C26-4C5B-94B5-492422EECEDA@xxxxxxxxxxxx> <20141222204857.GK24183@dastard> <6F43BF63-A44E-43F6-A184-9AAC10DDDFDF@xxxxxxxxxxxxxxx> <20141222223540.GS15665@dastard> <2F3F57BB-59EA-4FF9-9254-6A598DE7AC46@xxxxxxxxxxxxxxx> <20141223003237.GA4521@dastard> <258BE536A650F646814BA46CC06568980F6A8AD7@xxxxxxxxxxxxxx> <20141223024248.GC4521@dastard>

Attachment: trace-xfs.out.gz
Description: GNU Zip compressed data

I had these errors running the trace-cmd report.
trace-cmd: No such file or directory
  function scsi_trace_parse_cdb not defined
  failed to read event print fmt for scsi_dispatch_cmd_start
  function scsi_trace_parse_cdb not defined
  failed to read event print fmt for scsi_dispatch_cmd_error
  function scsi_trace_parse_cdb not defined
  failed to read event print fmt for scsi_dispatch_cmd_done
  function scsi_trace_parse_cdb not defined
  failed to read event print fmt for scsi_dispatch_cmd_timeout
  Error: expected 'field' but read 'print'
  failed to read event format for sys_enter_inotify_init
  Error: expected 'field' but read 'print'
  failed to read event format for sys_enter_sync
  Error: expected 'field' but read 'print'
  failed to read event format for sys_enter_vhangup
  Error: expected 'field' but read 'print'
  failed to read event format for sys_enter_munlockall
  Error: expected 'field' but read 'print'
  failed to read event format for sys_enter_getpgrp
  Error: expected 'field' but read 'print'
  failed to read event format for sys_enter_setsid
  Error: expected 'field' but read 'print'
  failed to read event format for sys_enter_restart_syscall
  Error: expected 'field' but read 'print'
  failed to read event format for sys_enter_pause
  Error: expected 'field' but read 'print'
  failed to read event format for sys_enter_getpid
  Error: expected 'field' but read 'print'
  failed to read event format for sys_enter_getppid
  Error: expected 'field' but read 'print'
  failed to read event format for sys_enter_getuid
  Error: expected 'field' but read 'print'
  failed to read event format for sys_enter_geteuid
  Error: expected 'field' but read 'print'
  failed to read event format for sys_enter_getgid
  Error: expected 'field' but read 'print'
  failed to read event format for sys_enter_getegid
  Error: expected 'field' but read 'print'
  failed to read event format for sys_enter_gettid
  Error: expected 'field' but read 'print'
  failed to read event format for sys_enter_sched_yield
On Dec 22, 2014, at 9:42 PM, Dave Chinner <david@xxxxxxxxxxxxx> wrote:

On Tue, Dec 23, 2014 at 02:12:15AM +0000, Weber, Charles (NIH/NIA/IRP) [E] wrote:
here you go

# xfs_db -c "inode 131" -c p /dev/dm-7

Nothing obviously wrong there, so there's no clear indication of why
the quota initialisation failed. If hasn't got to quotacheck,
because theat throws verbos errors when it fails, so it's something
going wrong during initialisation.

Just to narrow it down, if you mount with just uquota does the
mount succeed? Please post the dmesg output whatever the outcome.
Does mounting with just pquota succeed? If neither succeed, what
happens if you mount with no quotas, then unmount and mount again
with quotas enabled?

If it still doesn't work, I'm going to need an event trace of a
failed mount (install trace-cmd and run:

# trace-cmd record -e xfs\* mount -o uquota,pquota /dev/dm-7 /mnt/pt
<some output>
# trace-cmd report > trace.out

And then compress the trace.out file and attach it.

Cheers,

Dave.
--
Dave Chinner
david@xxxxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>