Re: weird quota issue

Weber, Charles (NIH/NIA/IRP) [C]
2014-12-23T18:48:37Z

[-- Attachment #1.1: Type: text/plain, Size: 3235 bytes --]

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@fromorbit.com> 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@fromorbit.com

[-- Attachment #1.2.1: Type: text/html, Size: 213 bytes --]

[-- Attachment #1.2.2: trace-xfs.out.gz --]
[-- Type: application/x-gzip, Size: 5400 bytes --]

[-- Attachment #1.2.3: Type: text/html, Size: 8933 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]