On 8/30/07, Chris Kirby <chris.kirby at sun.com> wrote: > Richard Lowe wrote: > > Boyd Adamson <boyd-adamson at usa.net> writes: > > > > > >>Chris Kirby <chris.kirby at sun.com> writes: > >> > >>>None of {ZFS,QFS,UFS} even bother to grab a lock in their statvfs > >>>handlers, so as Boyd Adamson correctly pointed out, all of the statvfs > >>>values are rumors at best anyway. > >> > >>Actually, that wasn't me. I pointed out that the free space at this > >>moment is no guide as to the free space when we actually come to write > >>the files. > >> > > > > > > And that surely the right thing to do here is to have the application > > either deal with EOVERFLOW sanely, or use the largefile environment. > > No doubt, that's definitely the best solution in general. > > The request for this RFE was to see if we could do something reasonable > for apps that can't be fixed for whatever reason (no maintainer, no > source code, etc.). That's what I'm trying to explore. :-)
If only there were a way to detect which apps were in that state :)