devd question

2009-02-28 Thread Michael Sperber
I'm trying to make devd run an stty command whenever a USB serial device is attached. Unfortunately, $device-name is ucom[0-9] and the device names are /dev/cuaU[0-9] - how do I get the correct name in the device action? I haven't found a way to extract the number by itself, so I'm stuck with sp

Re: ZFS root File System

2009-02-28 Thread Dillon Kass
Xin LI wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dr. Aharon Friedman wrote: (note the fact that / can not be easily rolled back to previous state using ZFS's snapshot feature, and can not be easily switched between clones I actually keep a full minimal install on my UFS /bootdis

Re: devd question

2009-02-28 Thread Kostik Belousov
On Sat, Feb 28, 2009 at 02:13:10PM +0100, Michael Sperber wrote: > > I'm trying to make devd run an stty command whenever a USB serial device > is attached. Unfortunately, $device-name is ucom[0-9] and the device > names are /dev/cuaU[0-9] - how do I get the correct name in the device > action?

Re: Question about disk schedulers

2009-02-28 Thread Luigi Rizzo
On Sat, Feb 28, 2009 at 01:47:07AM -0500, Yoshihiro Ota wrote: > Hi, Luigi and Fabio: > > I have a question about the GEOM disk scheduler you announed a while ago. > http://lists.freebsd.org/pipermail/freebsd-stable/2009-January/047597.html > > Can you tell me how does the scheduler interact with

Re: ZFS root File System

2009-02-28 Thread Clifton Royston
On Fri, Feb 27, 2009 at 07:21:15PM -0800, Matthew Dillon wrote: > My experience with one of our people trying to do the same thing > w/ HAMMER... we got it working, but it is not necessarily cleaner. > > I'd rather just boot from a small UFS /boot partition on 'a' (256M > or 512M)

vm_thread_new: kstack allocation failed with vm.kmem_size="1536M"

2009-02-28 Thread Pete French
So, I have a farm of machines runnign 7.1/amd64, all of which have 16 gig of memory in them. This afternoon, as an experiment, I altered loader.conf to have these two lines in it: vm.kmem_size="1536M" vm.kmem_size_max="1536M" This is what I do on machines running ZFS - these machines are not, how

Re: vm_thread_new: kstack allocation failed with vm.kmem_size="1536M"

2009-02-28 Thread Dan Nelson
In the last episode (Feb 28), Pete French said: > So, I have a farm of machines runnign 7.1/amd64, all of which have 16 gig > of memory in them. This afternoon, as an experiment, I altered > loader.conf to have these two lines in it: > > vm.kmem_size="1536M" > vm.kmem_size_max="1536M" > > This i

Re: vm_thread_new: kstack allocation failed with vm.kmem_size="1536M"

2009-02-28 Thread Pete French
> You've probably reduced kmem_size from the default. I don't set anything on > my 6 GB amd64 system, and I get: > > $ sysctl vm.kmem_size vm.kmem_size_max > vm.kmem_size: 2061496320 > vm.kmem_size_max: 3865468109 > > I assume your 16GB system would default to even larger numbers. What values > d

Re: vm_thread_new: kstack allocation failed with vm.kmem_size="1536M"

2009-02-28 Thread Dan Nelson
In the last episode (Mar 01), Pete French said: > > You've probably reduced kmem_size from the default. I don't set > > anything on my 6 GB amd64 system, and I get: > > > > $ sysctl vm.kmem_size vm.kmem_size_max > > vm.kmem_size: 2061496320 > > vm.kmem_size_max: 3865468109 > > > > I assume your 16

Re: 7.1 new install halts on BTX error

2009-02-28 Thread David Adam
On Wed, 25 Feb 2009, Gavin Atkinson wrote: > On Thu, 2009-01-29 at 12:13 +0900, David Adam wrote: > > I upgraded my 7.0 system to 7.1-RELEASE with freebsd-update only to find > > that it no longer boots correctly, instead crashing with a BTX backtrace. > > If I break to the loader prompt and use