Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-amd64
Navigation:
Lists: gentoo-amd64: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-amd64@g.o
From: "Mark Knecht" <markknecht@...>
Subject: Re: nfs mount has now become read-only
Date: Tue, 4 Apr 2006 15:45:18 -0700
On 4/4/06, Jürgen Schinker <ba1020@...> wrote:
> On Tue, April 4, 2006 02:11, Mark Knecht wrote:
>
> why do you mount with such large write buffer ?
> wsize=32768
>
> Jürgen
>

Hi Jurgen,
   It was suggested some long time ago, possibly on the Gentoo-users
list or maybe a Redhat list. The little machine has a fairly slow disk
drive and serves as a remote disk for our MythTV tuners. The tuners
exist in another machine and they send all TV data across the network
to get written to this disk. It seemed that using a large write buffer
might be a good idea for ensuring we didn't drop data when recording.

Thanks,
Mark

-- 
gentoo-amd64@g.o mailing list


References:
nfs mount has now become read-only
-- Mark Knecht
Re: nfs mount has now become read-only
-- Jürgen Schinker
Navigation:
Lists: gentoo-amd64: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: nfs mount has now become read-only
Next by thread:
udevd event find_free_number?
Previous by date:
Re: nfs mount has now become read-only
Next by date:
Re: nfs mount has now become read-only


Updated Jun 17, 2009

Summary: Archive of the gentoo-amd64 mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.