Ok, that makes sense. Thanks. By the way, Eric, were you able to reproduce the bug I mentioned earlier?
It has proven itself to be very difficult to trigger. I received several reports of successfull 24-hour ztest runs, only 1 user has been affected. I've changed the ztest attach/detach frequency to "always", and was able to reproduce it once in 10 minutes. I think I was lucky, because I tried to reproduce it again and even after 10 hours I wasn't able to do it.. I have the core file available, but I haven't analyzed the cause yet. On Tuesday 20 June 2006 21:16, Eric Schrock wrote: > Actually, this was intentionally not put in zfs_namecheck() due to > backwards compatibility issues. If you already had a pool named > 'raidz_something', then if we put the check in zfs_namecheck(), you > wouldn't be able to do _anything_ to the pool. See the comment in > zpool_name_valid(): > > /* > * The rules for reserved pool names were extended at a later point. > * But we need to support users with existing pools that may now be > * invalid. So we only check for this expanded set of names during > a * create (or import), and only in userland. > */ > > - Eric > > -- > Eric Schrock, Solaris Kernel Development > http://blogs.sun.com/eschrock
