Le 30 mars 08 à 15:57, Kyle McDonald a écrit :
> Fred Oliver wrote:
>>
>> Marion Hakanson wrote:
>>> [EMAIL PROTECTED] said:
I am having trouble destroying a zfs file system (device busy) and
fuser
isn't telling me who has the file open: . . .
This situation appears to occur e
Kyle McDonald wrote:
> In this case you may need to use 'zfs unshare', since I don't know if
> 'unshare' can unshare a ZFS that was sared by 'zfs share'.
This makes no difference:
# zfs unshare files/custfs/cust12/2053699a
cannot unshare 'files/custfs/cust12/2053699a': not currently shared
# zf
Fred Oliver wrote:
>
> Marion Hakanson wrote:
>> [EMAIL PROTECTED] said:
>>> I am having trouble destroying a zfs file system (device busy) and
>>> fuser
>>> isn't telling me who has the file open: . . .
>>> This situation appears to occur every night during a system test.
>>> The only
>>> pecul
Fred Oliver wrote:
> I am having trouble destroying a zfs file system (device busy) and fuser
> isn't telling me who has the file open:
>
> # zfs destroy files/custfs/cust12/2053699a
> cannot unmount '/files/custfs/cust12/2053699a': Device busy
>
> # zfs unmount files/custfs/cust12/2053699a
> cann
Richard Elling wrote:
> Fred Oliver wrote:
>> I am having trouble destroying a zfs file system (device busy) and
>> fuser isn't telling me who has the file open:
>>
>> # zfs destroy files/custfs/cust12/2053699a
>> cannot unmount '/files/custfs/cust12/2053699a': Device busy
>>
>> # zfs unmount file
Fred Oliver wrote:
> I am having trouble destroying a zfs file system (device busy) and fuser
> isn't telling me who has the file open:
>
> # zfs destroy files/custfs/cust12/2053699a
> cannot unmount '/files/custfs/cust12/2053699a': Device busy
>
> # zfs unmount files/custfs/cust12/2053699a
> cann
Marion Hakanson wrote:
[EMAIL PROTECTED] said:
I am having trouble destroying a zfs file system (device busy) and fuser
isn't telling me who has the file open:
. . .
This situation appears to occur every night during a system test. The only
peculiar operation on the errant file system is tha
[EMAIL PROTECTED] said:
> I am having trouble destroying a zfs file system (device busy) and fuser
> isn't telling me who has the file open:
> . . .
> This situation appears to occur every night during a system test. The only
> peculiar operation on the errant file system is that another system
[EMAIL PROTECTED] said:
> When i modify zfs FS propreties I get "device busy"
> -bash-3.00# zfs set mountpoint=/mnt1 pool/zfs1 cannot unmount '/mnt': Device
> busy
> Do you know how to identify porcess accessing this FS ? fuser doesn't work
> with zfs!
Actually, fuser works fine with ZFS here.
Carol,
Probably "/mnt" is already in use ie. some other filesystem is mounted
there.
Can you please verify ?
What is the original mountpoint of pool/zfs1 ?
Regards,
Sanjeev.
Caroline Carol wrote:
> Hi all,
>
> When i modify zfs FS propreties I get "device busy"
>
> -bash-3.00# zfs set moun
10 matches
Mail list logo