Problems with ZFS on AMD64 (and i386 now)

[tlott at gamesnet.de]

> On Tue, Sep 15, 2009 at 11:55:11PM +0200, Tobias Lott wrote:
>>
>>
>> On Tue, 15 Sep 2009 23:41:42 +0200
>> Pawel Jakub Dawidek <pjd at FreeBSD.org> wrote:
>>
>> > On Tue, Sep 15, 2009 at 08:44:04PM +0200, Tobias Lott wrote:
>> > > Any news on this?
>> >
>> > Not really. I'm out of ideas. A way to repoduce it would be of course
>> > best. If you can't provide one maybe you remember something strange
>> > just before panic, like disk disappeared or something?
>> >
>>
>> Looks like I've found whats causing it by mounting all ZFS Volumes one
>> by one. It was a Volume used by a Jail running nginx, nagios and some
>> other stuff.
>> Weird but luckily not that important since its a Test Machine, can I
>> provide anything that you could figure out whats wrong with that Volume
>> so it can be fixed? Cause I triggered
>> this only by upgrading BETA3->4 #3 r196936.
>
> What do you mean by 'ZFS Volume' here? You mean ZVOL as created with
> 'zfs create -V' command? Could you tell me exactly what steps should I
> take to reproduce the problem?
>
> --
> Pawel Jakub Dawidek                       http://www.wheel.pl
> pjd at FreeBSD.org                           http://www.FreeBSD.org
> FreeBSD committer                         Am I Evil ? Yes, I Am!
>

No sorry bad wording from my Side, its just a normal ZFS Filesystem (zfs
create tank/filesystem) created some more Filesystem for more Jails on the
same Machine yesterday.
Couldn't reproduce it so far, so I guess it was just an update gone wrong
with the result of one corrupted Filesystem.