On Sun, Jun 29, 2008 at 8:34 PM, Matthew Gardiner <[EMAIL PROTECTED]>
wrote:
>
>
> 2008/6/30 Tim <[EMAIL PROTECTED]>:
>
>
>>
>> On Sun, Jun 29, 2008 at 8:30 PM, Matthew Gardiner <
>> [EMAIL PROTECTED]> wrote:
>>
>>> I think Kyle might be onto something here. With ZFS it is so easy
to create
2008/6/30 Tim <[EMAIL PROTECTED]>:
>
>
> On Sun, Jun 29, 2008 at 8:30 PM, Matthew Gardiner <
> [EMAIL PROTECTED]> wrote:
>
>> I think Kyle might be onto something here. With ZFS it is so easy
>>> to create file systems, one could expect many people to do so.
>>> In the past, it was so difficult a
Richard Elling wrote:
>> I consider it a bug if my machine doesn't boot up because one single,
>> non-system and non-mandatory, FS has an issue and doesn't mount. The
>> rest of the machine should still boot and function fine.
>>
>
> I think Kyle might be onto something here.
I tend to agr
On Sun, Jun 29, 2008 at 8:30 PM, Matthew Gardiner <[EMAIL PROTECTED]>
wrote:
> I think Kyle might be onto something here. With ZFS it is so easy
>> to create file systems, one could expect many people to do so.
>> In the past, it was so difficult and required planning, so people
>> tended to be m
>
> I think Kyle might be onto something here. With ZFS it is so easy
> to create file systems, one could expect many people to do so.
> In the past, it was so difficult and required planning, so people
> tended to be more careful about mount points.
>
> In this new world, we don't really have a w
Kyle McDonald wrote:
> michael schuster wrote:
>
>> Charles Soto wrote:
>>
>>
>>> On 6/27/08 8:55 AM, "Mark J Musante" <[EMAIL PROTECTED]> wrote:
>>>
>>>
>>>
On Fri, 27 Jun 2008, wan_jm wrote:
> the procedure is follows:
> 1. mkdir
On Sun, 29 Jun 2008 08:39:17 -0400
Kyle McDonald <[EMAIL PROTECTED]> wrote:
> I consider it a bug if my machine doesn't boot up because one single,
> non-system and non-mandatory, FS has an issue and doesn't mount. The
> rest of the machine should still boot and function fine.
My system has alw
michael schuster wrote:
> Charles Soto wrote:
>
>> On 6/27/08 8:55 AM, "Mark J Musante" <[EMAIL PROTECTED]> wrote:
>>
>>
>>> On Fri, 27 Jun 2008, wan_jm wrote:
>>>
>>>
the procedure is follows:
1. mkdir /tank
2. touch /tank/a
3. zpool create tank c0d0p3
this
Charles Soto wrote:
> On 6/27/08 8:55 AM, "Mark J Musante" <[EMAIL PROTECTED]> wrote:
>
>> On Fri, 27 Jun 2008, wan_jm wrote:
>>
>>> the procedure is follows:
>>> 1. mkdir /tank
>>> 2. touch /tank/a
>>> 3. zpool create tank c0d0p3
>>> this command give the following error message:
>>> cannot mount
On 6/27/08 8:55 AM, "Mark J Musante" <[EMAIL PROTECTED]> wrote:
> On Fri, 27 Jun 2008, wan_jm wrote:
>
>> the procedure is follows:
>> 1. mkdir /tank
>> 2. touch /tank/a
>> 3. zpool create tank c0d0p3
>> this command give the following error message:
>> cannot mount '/tank': directory is not empt
On Fri, Jun 27, 2008 at 6:30 PM, wan_jm <[EMAIL PROTECTED]> wrote:
> I just have a try.
> In my opinion, if the directory is not empty, zpool should not create the
> pool.
>
> let me give a senario if some day our software runs on the customer site. but
> one engineer of the customer did the abov
I don't know why that zfs mount failed stops all the other network service.
maybe it is not a bug of zfs. it must a bug with SMF in my opinion. do you
think so
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensola
I just have a try.
In my opinion, if the directory is not empty, zpool should not create the pool.
let me give a senario if some day our software runs on the customer site. but
one engineer of the customer did the above operation failed, but he didn't do
anything more. few days later , the os a
On Fri, 27 Jun 2008, wan_jm wrote:
> the procedure is follows:
> 1. mkdir /tank
> 2. touch /tank/a
> 3. zpool create tank c0d0p3
> this command give the following error message:
> cannot mount '/tank': directory is not empty;
> 4. reboot.
> then the os can only be login in from console. does it a
Hi,
why are you creating a file in the directory tank?
Matthew
2008/6/27 wan_jm <[EMAIL PROTECTED]>:
> the procedure is follows:
> 1. mkdir /tank
> 2. touch /tank/a
> 3. zpool create tank c0d0p3
> this command give the following error message:
> cannot mount '/tank': directory is not empty;
> 4
the procedure is follows:
1. mkdir /tank
2. touch /tank/a
3. zpool create tank c0d0p3
this command give the following error message:
cannot mount '/tank': directory is not empty;
4. reboot.
then the os can only be login in from console. does it a bug?
This message posted from opensolaris.org
__
16 matches
Mail list logo
