Date: Thu, 17 Feb 2011 00:31:52 +0100 From: Anders Andersson <pipatron@gmail.com> To: Andrew Thompson <andy@fud.org.nz> Cc: freebsd-fs@freebsd.org Subject: Re: zfs directory listing Message-ID: <AANLkTin92Qu4VoiSiSydGmNofuCGSd7tY7H93_BHpmKu@mail.gmail.com> In-Reply-To: <AANLkTinwRumkvSn7wfh4a%2BeNJyFoFDyMMKjk7GOSLAXc@mail.gmail.com> References: <AANLkTinwRumkvSn7wfh4a%2BeNJyFoFDyMMKjk7GOSLAXc@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> mqueue has a link count of 522824. I can not list the contents of this > directory, when I do the number of read IOPS sits > 100 and it will > never complete > if I ^C the ls then the read ops drops back to zero. If I leave a `ls` > or `find /var/spool/mqueue` running then they will churn the disks > indefinitely without producing output. Now, I just joined to get help from UFS2-people, but when I am doing things like this in linux, I use "ls -lU" or "ls -lf". "ls -U" means that it doesn't try to sort the entries at all, but outputs them in the order they are found. This means that there is no longer a delay from collecting them in memory and sorting, but it outputs each entry as soon as they are found. This may help you unless there is something else wrong, or unless such a flag does not exist in your version of ls. You also have the utility "find", which might work better in this case. Forgive me if these seem trivial and obvious. :) // pipe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTin92Qu4VoiSiSydGmNofuCGSd7tY7H93_BHpmKu>