Author: Brian May <brian@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 12 Dec 2012 09:19:44 +1100
On 12 December 2012 09:14, Ben Myers <bpm@xxxxxxx> wrote: Looks like that would be print out of fs_table_initialise_projects. 40 static int 41 fs_device_number( 42 const char *name,
Hey Brian, Looks like that would be print out of fs_table_initialise_projects. 40 static int 41 fs_device_number( 42 const char *name, 43 dev_t *devnum) 44 { 45 struct stat64 sbuf; 46 47 if (stat64(n
Can you test a current upstream version and if it fails post the full strace output? There's been some changes recently for quota iteration bugs that may avoid/fix this issue... Cheers, Dave. -- Dave
D'oh. I guess that fs_cursor_next_entry is the next candidate: 355 /* 356 * Given a directory, match it up to a filesystem mount point. 357 */ 358 static struct fs_path * 359 fs_mount_point_from_path
Author: Brian May <brian@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 12 Dec 2012 09:45:29 +1100
On 12 December 2012 09:37, Ben Myers <bpm@xxxxxxx> wrote: Hmm. There are some recent commits that look related. Commit 36298cced and 19473a2ac. Can you try with this code? git://oss.sgi.com/xfs/cm
fs_mount_point_from_path() probably needs to set errno to ENOENT or something when the dir provided isn't in whatever "fs_cursor" is traversing (tree?). -Alex
I haven't got the email yet, but I've looked at it in the archives... What's the contents of /proc/self/mounts? The error is coming from setting up the project paths in the table. It appears to be is
No, but it's most likely the same problem as fixed in commit 19473a2ac. Can you add this to quota/quot.c:quot_init(): + quot_cmd.flags = CMD_FLAG_GLOBAL; And see if the problem goes away? Cheers, Dav
Author: Brian May <brian@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 19 Mar 2013 15:51:30 +1100
No, but it's most likely the same problem as fixed in commit 19473a2ac. Can you add this to quota/quot.c:quot_init(): + Â Â Â quot_cmd.flags = CMD_FLAG_GLOBAL; And see if the problem goes away? I ma
Which tells me exactly what is happening. The project quotas are not on the filesystem you directed the the quota command at, and xfs_quota is telling you that it can't find the mount point for the c
Author: Brian May <brian@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 20 Mar 2013 16:19:16 +1100
On 19 March 2013 17:31, Dave Chinner <david@xxxxxxxxxxxxx> wrote: Which tells me exactly what is happening. The project quotas are not on the filesystem you directed the the quota command at, and xfs
Because the quota command does mount point and project quota initialisation (i.e. global state) before it parses any specific command. The issues project quota configuration is global information, an