I've experienced a hang (cannot re-establish lost VNC session, ssh as
me, console login as root) on an snv_80+ system. CTEact tells me:
Searching for mutex deadlocks: ### MUTEX ###
thread 2a102765ca0 is waiting for mutex 0x3000466e5c8
mutex is owned by thread 2a
> such a minor "feature"
I don't think copying files is a minor feature.
Doubly so since the words I've read from Sun suggest that ZFS "file systems"
(or "data sets" or whatever they are called now) can be used in the way
directories on a normal file system are used.
This message posted f
sudarshan sridhar wrote:
> Hi,
>
> How zfs does the fiile/directory traversel by reading each dnode
> DIRECTORY entry?
>
> How the creation/deletion of a file works.
>
> Could anybody please explain related information along with
> datastructures. More internal details would be a great he
[EMAIL PROTECTED] wrote:
> On Thu, 27 Dec 2007, [EMAIL PROTECTED] wrote:
>
>>
>>>
>>> I would guess that this is caused by different st_dev values in the new
>>> filesystem. In such a case, mv copies the files instead of renaming
>>> them.
>>
>>
>> No, it's because they are different filesystems a
when I remove a separate zil disk from a pool, the pool continues to function,
logging synchronous writes to the disks in the pool. Status shows that the log
disk has been removed, and everything seems to work fine until I export the
pool.
After the pool has been exported (long after the log di
On Thu, 27 Dec 2007, [EMAIL PROTECTED] wrote:
>
>>
>> I would guess that this is caused by different st_dev values in the new
>> filesystem. In such a case, mv copies the files instead of renaming them.
>
>
> No, it's because they are different filesystems and the data needs to be
> copied; zfs do
>
>I would guess that this is caused by different st_dev values in the new
>filesystem. In such a case, mv copies the files instead of renaming them.
No, it's because they are different filesystems and the data needs to be
copied; zfs doesn't allow data movement between filesystems within a poo
Darren Reed <[EMAIL PROTECTED]> wrote:
> Having just done a largish mv from one ZFS filesystem to another ZFS
> filesystem in the same zpool, I was somewhat surprised at how long it
> took - I was expecting it to be near instant like it would be within the
> same filesystem.
I would guess that th
