On 08/26/15 10:53, Loris Bennett wrote: > Hi Thomas, > > LEIBOVICI Thomas <[email protected]> writes: > >> Hi Loris, >> >> robinhood updates --fs-info and --user-info on-the-fly to make them instantly >> available when you query it >> (this feature is known as "accounting" and is activated by {user,group}_acct >> parameters). >> >> Unlike fs-info and user-info, top-dirs is generated at the time you query it >> and >> is a very expensive request >> so it is expected to be much longer. >> >> However, in you case, I can't explain why it already returned 1 directory and >> don't print the 4 others >> as it did most of the sorting job if it could print the first directory. >> Perhaps there is a stuck DB request. You can check by running: >> >> mysql <your_db> >>> show process list; > I did 'show processlist;'. Apart from I bunch of sleeping processes I > have > > INSERT INTO > ENTRIES(id,owner,gr_name,size,blocks,last_access,last_mod,type,mode,nlink,md_update,inva > > which is presumably from the currently running scan and > > Copying to tmp table | SELECT parent_id, COUNT(*) as dirattr_sort FROM > NAMES GROUP BY parent_id ORDER BY dirattr_sort DESC The top dirs request looks to run normally. Are you sure top-dirs already returned 1 directory? I would expect it displays them all at the same time. > > Is that what I should see and is the running scan causing the slowness? >
Of course the concurrency between the running scan and the topdirs query doesn't help. Anyhow, it is expected this request is long. For example you can run it daily in a cron, but don't expect to have a real-time / frequent usage of it. Regards. ------------------------------------------------------------------------------ _______________________________________________ robinhood-support mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/robinhood-support
