Re: Why is TUNABLE_INT discouraged?

2010-08-08 Thread Garrett Cooper
2010/8/7 Ivan Voras ivo...@freebsd.org: 2010/8/8 Dag-Erling Smørgrav d...@des.no: Garrett Cooper gcoo...@freebsd.org writes: Dag-Erling Smørgrav d...@des.no writes: Perhaps.  I don't remember all the details; I can't find a discussion in the list archives (other than me announcing the

Re: glabel force sectorsize patch

2010-08-08 Thread Pawel Jakub Dawidek
On Sun, Aug 08, 2010 at 03:57:44AM +0200, Ivan Voras wrote: Hi, In order to help users having 4k sector drives which the system recognizes as 512 byte sector drives, I'm proposing a patch to glabel which enables it to use a forced sector size for its native-labeled providers. It is

Re: glabel force sectorsize patch

2010-08-08 Thread Pawel Jakub Dawidek
On Sun, Aug 08, 2010 at 02:02:17PM +0200, Ivan Voras wrote: On 8.8.2010 12:30, Pawel Jakub Dawidek wrote: So why do you want to obfuscate glabel with it? For people to start depend on it? Once we start supporting 4kB sectors what do we do with such a change? Remove it and decrease version

Re: Why is TUNABLE_INT discouraged?

2010-08-08 Thread Ed Maste
On Sun, Aug 08, 2010 at 01:30:19AM +0200, Ivan Voras wrote: 2010/8/8 Dag-Erling Sm??rgrav d...@des.no: Garrett Cooper gcoo...@freebsd.org writes: Dag-Erling Sm??rgrav d...@des.no writes: Perhaps. ??I don't remember all the details; I can't find a discussion in the list archives (other

Re: glabel force sectorsize patch

2010-08-08 Thread Pawel Jakub Dawidek
On Sun, Aug 08, 2010 at 02:57:20PM +0200, Marius Nünnerich wrote: On Sun, Aug 8, 2010 at 14:02, Ivan Voras ivo...@freebsd.org wrote: I'd like to hear comments from the wider audience. In respect with your comment, I will compromise: as 4k sector drives have become available over the counter

Re: glabel force sectorsize patch

2010-08-08 Thread Marius Nünnerich
On Sun, Aug 8, 2010 at 14:02, Ivan Voras ivo...@freebsd.org wrote: On 8.8.2010 12:30, Pawel Jakub Dawidek wrote: On Sun, Aug 08, 2010 at 03:57:44AM +0200, Ivan Voras wrote: Hi, In order to help users having 4k sector drives which the system recognizes as 512 byte sector drives, I'm proposing

Re: sched_pin() versus PCPU_GET

2010-08-08 Thread Attilio Rao
2010/8/4 m...@freebsd.org: On Fri, Jul 30, 2010 at 2:31 PM, John Baldwin j...@freebsd.org wrote: On Friday, July 30, 2010 10:08:22 am John Baldwin wrote: On Thursday, July 29, 2010 7:39:02 pm m...@freebsd.org wrote: We've seen a few instances at work where witness_warn() in ast() indicates

Re: sched_pin() versus PCPU_GET

2010-08-08 Thread mdf
On Sun, Aug 8, 2010 at 2:43 PM, Attilio Rao atti...@freebsd.org wrote: 2010/8/4  m...@freebsd.org: On Fri, Jul 30, 2010 at 2:31 PM, John Baldwin j...@freebsd.org wrote: On Friday, July 30, 2010 10:08:22 am John Baldwin wrote: On Thursday, July 29, 2010 7:39:02 pm m...@freebsd.org wrote:

Re: Why is TUNABLE_INT discouraged?

2010-08-08 Thread M. Warner Losh
In message: 20100808130624.gb40...@sandvine.com Ed Maste ema...@freebsd.org writes: : On Sun, Aug 08, 2010 at 01:30:19AM +0200, Ivan Voras wrote: : : 2010/8/8 Dag-Erling Sm??rgrav d...@des.no: : Garrett Cooper gcoo...@freebsd.org writes: : Dag-Erling Sm??rgrav d...@des.no writes:

Re: glabel force sectorsize patch

2010-08-08 Thread Marius Nünnerich
On Sun, Aug 8, 2010 at 21:08, Ivan Voras ivo...@freebsd.org wrote: On 8.8.2010 14:57, Marius Nünnerich wrote: On Sun, Aug 8, 2010 at 14:02, Ivan Voras ivo...@freebsd.org wrote: This mechanism is a band-aid until there's a better way of dealing with 4k drives. I do not like this at all. Even

Re: Why is TUNABLE_INT discouraged?

2010-08-08 Thread Garrett Cooper
On Sun, Aug 8, 2010 at 11:14 AM, M. Warner Losh i...@bsdimp.com wrote: In message: 20100808130624.gb40...@sandvine.com            Ed Maste ema...@freebsd.org writes: : On Sun, Aug 08, 2010 at 01:30:19AM +0200, Ivan Voras wrote: : : 2010/8/8 Dag-Erling Sm??rgrav d...@des.no: : Garrett

Re: NFS server hangs (was no subject)

2010-08-08 Thread Rick Macklem
I have a similar problem. I have a NFS server (8.0 upgraded a couple times since Feb 2010) that locks up and requires a reboot. The clients are busy vm's from VMWare ESXi using the NFS server for vmdk virtual disk storage. The ESXi reports nfs server inactive and all the vm's post