On Thu, 18 Mar 2004, Kyryll A Mirnenko wrote:
> >Using "tunefs -m". You need to be really careful doing this, and read
> >the man page for tunefs again, particularly the warning about how
> >lowering this number can trash your filesystem's performance.
>
> I don't want that, I need to allow usin
>Using "tunefs -m". You need to be really careful doing this, and read
>the man page for tunefs again, particularly the warning about how
>lowering this number can trash your filesystem's performance.
I don't want that, I need to allow using preserved 8% of disk space to a little
group of non-r
At 2004-03-17T06:59:39Z, Kyryll A Mirnenko <[EMAIL PROTECTED]> writes:
> Thanks, thats what I want. So that means nobody but root can write to
> that preserved (with `tunefs -m`) space? How can I allow more users to
> do that?
Buy more disk. Seriously. Don't mess with this value unless yo
>
> That's an old problem, but yesterday I was working with 1.4G UFS2-slice
> reported by `df` to have 400kb of free space. Alternative calculations (e.g.
> writing a random file until kernel says no inode's free) give a result of
> more that 100M (!) unused. Thats about 7% of the whole size!
On Wed, 17 Mar 2004, Kyryll A Mirnenko wrote:
> Thanks, thats what I want. So that means nobody but root can write
> to that preserved (with `tunefs -m`) space? How can I allow more users
> to do that?
Using "tunefs -m". You need to be really careful doing this, and read
the man page for tunefs
Thanks, thats what I want. So that means nobody but root can write to that preserved
(with `tunefs -m`) space? How can I allow more users to do that?
(my mail server crashed on friday, so I didn't receive freebsd digest about this)
--
Укрпост - продвинутая почта. http://www.ukrpost.net/
IMAP
On Tue, Mar 16, 2004 at 02:31:11AM +0200, Kyryll A Mirnenko wrote:
> So whats wrong with `df` (e.g. statfs/fstatfs)?
It's not a bug, any more than it was when you asked on Friday.
--
Matthew Hunt <[EMAIL PROTECTED]> * Salvage, like other forms of virtue, is
http://www.pobox.com/~mph/
Kyryll A Mirnenko wrote:
That's an old problem, but yesterday I was working with 1.4G UFS2-slice
reported by `df` to have 400kb of free space. Alternative calculations (e.g.
writing a random file until kernel says no inode's free) give a result of
more that 100M (!) unused. Thats about 7% of t
That's an old problem, but yesterday I was working with 1.4G UFS2-slice
reported by `df` to have 400kb of free space. Alternative calculations (e.g.
writing a random file until kernel says no inode's free) give a result of
more that 100M (!) unused. Thats about 7% of the whole size!
So whats