Hey Charles, On Fri, Aug 09, 2013 at 12:29:20PM -0400, Weber, Charles (NIH/NIA/IRP) [C] wrote: > When I referred to initialize I meant running xfs_quota -x project -s name Hmm. What if you used 'xfs_quota -x project -s -p /path/to/new/dirs name'? > When I run xfs_quota -x 'project -c lg' > > I do get warnings about project identifier and inheritance but only for the > new directories that I created and copied the large data sets into. I don't > get those warning about the earlier files and folders for a given project. Those warnings refer to not having a project id set in the inode core, and whether a directory will set it's project id into the inode cores of whatever you create inside. Without that project id set in the new files you create, the quota subsystem won't know which project quota to reserve blocks against. That's why your block usage wasn't changing. > When I run the project -s again it does update the block usage. Maybe the first try failed to find the new directory? I'm not sure. > But I would think the block usage should update automatically. Could you cut an paste the procedure to you used to create the new directories? Thanks, Ben _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
