On 9/29/06, Michael Phua - PTS <[EMAIL PROTECTED]> wrote:
Our customer has an Sun Fire X4100 with Solaris 10 using ZFS and a HW RAID
array (STK D280).
He has extended a LUN on the storage array and want to make this new size
known to ZFS and Solaris.
Does anyone know if this can be done and how i
Hi,
Our customer has an Sun Fire X4100 with Solaris 10 using ZFS and a HW RAID
array (STK D280).
He has extended a LUN on the storage array and want to make this new size
known to ZFS and Solaris.
Does anyone know if this can be done and how it can be done.
Cheers!
Warm regards.
Michael Phua
On Thu, Sep 28, 2006 at 05:36:16PM +0200, Robert Milkowski wrote:
> Hello Chris,
>
> Thursday, September 28, 2006, 4:55:13 PM, you wrote:
>
> CG> I keep thinking that it would be useful to be able to define a
> CG> zfs file system where all calls to mkdir resulted not just in a
> CG> directory bu
Frank Cusack wrote:
On September 27, 2006 11:27:16 AM -0700 Richard Elling - PAE
<[EMAIL PROTECTED]> wrote:
In the interim, does it makes sense for a simple rule of thumb?
For example, in the above case, I would not have the hole if I did
any of the following:
1. add one disk
2. remove o
On Fri, Sep 29, 2006 at 01:26:04AM +0200, [EMAIL PROTECTED] wrote:
>
> >Please elaborate: "CIFS just requires the automount hack."
>
>
> CIFS currently access the files through the local file system so
> it can invoke the automouter and there can use "tricky maps".
Well, Samba does. And it do
On September 27, 2006 11:27:16 AM -0700 Richard Elling - PAE <[EMAIL
PROTECTED]> wrote:
In the interim, does it makes sense for a simple rule of thumb?
For example, in the above case, I would not have the hole if I did
any of the following:
1. add one disk
2. remove one disk
>Please elaborate: "CIFS just requires the automount hack."
CIFS currently access the files through the local file system so
it can invoke the automouter and there can use "tricky maps".
Casper
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
On Thu, Sep 28, 2006 at 12:40:17PM -0500, Ed Plese wrote:
> This can be elaborated on to do neat things like create a ZFS clone when
> a client connects and then destroy the clone when the client
> disconnects (via "root postexec"). This could possibly be useful for
> the shared build system that
This works like a champ:
smbclient -U foobar samba_server\\home
Given a UNIX account foobar with a smbpasswd for the account, the zfs
filesystem pool/home/foobar was created and smclient connected to it.
Thank you.
Ron Halstead
This message posted from opensolaris.org
_
On Thu, 2006-09-28 at 10:51 -0700, Richard Elling - PAE wrote:
> Keith Clay wrote:
> > We are in the process of purchasing new san/s that our mail server runs
> > on (JES3). We have moved our mailstores to zfs and continue to have
> > checksum errors -- they are corrected but this improves on th
Keith Clay wrote:
We are in the process of purchasing new san/s that our mail server runs
on (JES3). We have moved our mailstores to zfs and continue to have
checksum errors -- they are corrected but this improves on the ufs inode
errors that require system shutdown and fsck.
So, I am recomm
On Thu, Sep 28, 2006 at 09:00:47AM -0700, Ron Halstead wrote:
> Please elaborate: "CIFS just requires the automount hack."
Samba's smb.conf supports a "root preexec" parameter that allows a
program to be run when a share is connected to. For example, with
a simple script, createhome.sh, like,
#
On Wed, Sep 27, 2006 at 08:55:48AM -0600, Mark Maybee wrote:
> Patrick wrote:
> >So ... how about an automounter? Is this even possible? Does it exist ?
>
> *sigh*, one of the issues we recognized, when we introduced the new
> cheap/fast file system creation, was that this new model would stress
>
Please elaborate: "CIFS just requires the automount hack."
Ron
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
> > (And if you don't need it to work remotely automount could take care of it
> > if you think "cd" should be sufficient reason to create a directory)
>
> Maybe on unmount empty filesystems could be destroyed.
more general?
If we have "events" like a library-call to "mkdir" or "change-dir"
o
Hello Chris,
Thursday, September 28, 2006, 4:55:13 PM, you wrote:
CG> I keep thinking that it would be useful to be able to define a
CG> zfs file system where all calls to mkdir resulted not just in a
CG> directory but in a file system. Clearly such a property would not
CG> be inherited but in a
On Thu, Sep 28, 2006 at 05:29:27PM +0200, [EMAIL PROTECTED] wrote:
>
> >Any mkdir in a builds directory on a shared build machine. Would be
> >very cool because then every user/project automatically gets a ZFS
> >fileystems.
> >
> >Why map it to mkdir rather than using zfs create ? Because mkd
>Any mkdir in a builds directory on a shared build machine. Would be
>very cool because then every user/project automatically gets a ZFS
>fileystems.
>
>Why map it to mkdir rather than using zfs create ? Because mkdir means
>it will work over NFS or CIFS.
"NFS" will be fairly difficult becau
Folks,
We are in the process of purchasing new san/s that our mail server
runs on (JES3). We have moved our mailstores to zfs and continue to
have checksum errors -- they are corrected but this improves on the
ufs inode errors that require system shutdown and fsck.
So, I am recommending
Jeremy Teo wrote:
I keep thinking that it would be useful to be able to define a zfs
file system where all calls to mkdir resulted not just in a directory
but in a file system. Clearly such a property would not be inherited
but in a number of situations here it would be a really useful feature
Jeremy Teo wrote:
I keep thinking that it would be useful to be able to define a zfs
file system where all calls to mkdir resulted not just in a directory
but in a file system. Clearly such a property would not be inherited
but in a number of situations here it would be a really useful feature
I keep thinking that it would be useful to be able to define a zfs file system
where all calls to mkdir resulted not just in a directory but in a file system.
Clearly such a property would not be inherited but in a number of situations
here it would be a really useful feature.
Any example us
I keep thinking that it would be useful to be able to define a zfs file system
where all calls to mkdir resulted not just in a directory but in a file system.
Clearly such a property would not be inherited but in a number of situations
here it would be a really useful feature.
I can see there
Hello experts,
My client is thinking about changing one of their servers running Solaris 8
(NIS Hub to mention something) to a server running Solaris 10.
The question that i have given is to check the differences or if you wish the
status/stability of changing VXvm with DMP (Dynamic Multi Pathi
Gino Ruopolo writes:
> Thank you Bill for your clear description.
>
> Now I have to find a way to justify myself with my head office that
> after spending 100k+ in hw and migrating to "the most advanced OS" we
> are running about 8 time slower :)
>
> Anyway I have a problem much more se
On Sep 26, 2006, at 12:26 PM, Chad Leigh -- Shire.Net LLC wrote:
On Sep 26, 2006, at 12:24 PM, Mike Kupfer wrote:
"Chad" == Chad Leigh <-- Shire.Net LLC" <[EMAIL PROTECTED]>>
writes:
Chad> snoop does not show me the reply packets going back. What do I
Chad> need to do to go both ways?
I
> > Even if we're using FSS, Solaris seems unable to
> give a small amount of I/O resource to ZONEX's
> activity ...
> >
> > I know that FSS doesn't deal with I/O but I think
> Solaris should be smarter ..
>
> What about using ipqos (man ipqos)?
I'm not referring to "network I/O" but "storage I/
27 matches
Mail list logo
