On 15/08/06, Lori Alt <[EMAIL PROTECTED]> wrote:
Brian Hechinger wrote:
> On Fri, Jul 28, 2006 at 02:26:24PM -0600, Lori Alt wrote:
>
>>>What about Express?
>>
>>Probably not any time soon. If it makes U4,
>>I think that would make it available in Express late
>>this year.
>
>
> Is there a speci
Hello zfs-discuss,
I do have several pools in a SAN shared environment where some pools
are mounted by one server and some by another.
Now I can do 'zpool export A B C D'
But I can't do 'zpool import A B C D'
import -a isn't an option since I want import only those pools I
just expor
All pools were exported than I tried to import one-by-one and got this with
only a first pool.
bash-3.00# zpool export nfs-s5-p4 nfs-s5-s5 nfs-s5-s6 nfs-s5-s7 nfs-s5-s8
bash-3.00# zpool import nfs-s5-p4
cannot mount '/nfs-s5-p4/d5139': directory is not empty
cannot mount '/nfs-s5-p4/d5141': direc
Hi Eric,
Customer had come back saying.
I've tried this and it doesn't work. It still displays the size as 1 gig after saying it's bringing the lun back online.
Kindly advise.
Thanks
Jaganraj.J
Eric Schrock wrote On 08/15/06 20:49,:
[ For ZFS discussions, try 'zfs-discuss@opensolari
Kevin Maguire wrote:
Hi
Is the following an accurate sstatment of the current status with (for me) the
3 main commercial ackup software solutions out there
(1) Legato Networker - support coming in 7.3.2 patch due soon. Until then backups of ZFS
filesystems wont work at all as the acl(8) call
This was part of my original (unpublished) proposal, but deferred it for
a few reasons:
- We have discussed the possiblity of introducing pool-wide properties
for a variety of reasons (such as background scrubbing intervals). I
thought it best to delay dealing with the confluence of these opt
Eric Schrock schrieb:
This RFE is also required for crypto support, as the encryption
algorithm must be known when the filesystem is created It also has the
benefit of cleaning up the implementation of other creation-time
properties (volsize and volblocksize) that were previously special
cases.
On Tue, Aug 15, 2006 at 06:12:47PM -0400, Bill Sommerfeld wrote:
> On Tue, 2006-08-15 at 12:47 -0700, Eric Schrock wrote:
>
> > The copy-on-write nature of ZFS makes this extremely difficult,
> > particularly w.r.t. to snapshots. That's not to say it can't be solved,
> > only that it won't be sol
Hi
Is the following an accurate sstatment of the current status with (for me) the
3 main commercial ackup software solutions out there
(1) Legato Networker - support coming in 7.3.2 patch due soon. Until then
backups of ZFS filesystems wont work at all as the acl(8) calls will fail. But
will
Brian Hechinger wrote:
On Fri, Jul 28, 2006 at 02:26:24PM -0600, Lori Alt wrote:
What about Express?
Probably not any time soon. If it makes U4,
I think that would make it available in Express late
this year.
Is there a specific Nevada build you are going to target? I'd love to
start tes
On Tue, 2006-08-15 at 12:47 -0700, Eric Schrock wrote:
> The copy-on-write nature of ZFS makes this extremely difficult,
> particularly w.r.t. to snapshots. That's not to say it can't be solved,
> only that it won't be solved in the near term (i.e. within the next
> year). The timeframe for ZFS
Peter Bortas wrote:
On 8/15/06, David Dyer-Bennet <[EMAIL PROTECTED]> wrote:
On 8/15/06, Richard Elling - PAE <[EMAIL PROTECTED]> wrote:
> This can be configured with the local mail delivery agent. You
could even
> put incoming mail in someone's $HOME, however that isn't always a
good idea.
On 8/15/06, Frank Cusack <[EMAIL PROTECTED]> wrote:
On August 15, 2006 2:37:27 PM -0500 David Dyer-Bennet <[EMAIL PROTECTED]> wrote:
> Oy, Kerberos. Never heard of any place that actually *uses* it, and
Lots of places use it.
Intellectually, I'm sure that's true -- because that much work
w
Getting way off-topic, but here goes ...
On August 15, 2006 12:33:01 PM -0700 "Anton B. Rang" <[EMAIL PROTECTED]> wrote:
Delivering into $HOME raises some new failure modes if the home directory
servers are NFS
mounted, but otherwise often works OK. However, in some cases it's simply
impossibl
On Tue, Aug 15, 2006 at 02:57:50PM -0400, Bill Sommerfeld wrote:
>
> I'm deeply concerned about this requirement -- in short, basic
> principles of crypto hygene require both key and algorithm agility, and
> if you can't change this after creation, the ability of ZFS to resist
> cryptographic atta
On 8/15/06, Peter Bortas <[EMAIL PROTECTED]> wrote:
On 8/15/06, David Dyer-Bennet <[EMAIL PROTECTED]> wrote:
> On 8/15/06, Richard Elling - PAE <[EMAIL PROTECTED]> wrote:
>
> > This can be configured with the local mail delivery agent. You could even
> > put incoming mail in someone's $HOME, how
On 8/15/06, Anton B. Rang <[EMAIL PROTECTED]> wrote:
Delivering into $HOME raises some new failure modes if the home directory
servers are NFS mounted, but otherwise often works OK. However, in some cases
it's simply impossible--for instance, in a secure NFS environment where the
home director
On 8/15/06, David Dyer-Bennet <[EMAIL PROTECTED]> wrote:
On 8/15/06, Richard Elling - PAE <[EMAIL PROTECTED]> wrote:
> This can be configured with the local mail delivery agent. You could even
> put incoming mail in someone's $HOME, however that isn't always a good idea.
I've run across system
Delivering into $HOME raises some new failure modes if the home directory
servers are NFS mounted, but otherwise often works OK. However, in some cases
it's simply impossible--for instance, in a secure NFS environment where the
home directory can't be mounted without a Kerberos ticket.
I think
On Fri, Jul 28, 2006 at 02:26:24PM -0600, Lori Alt wrote:
> >What about Express?
> Probably not any time soon. If it makes U4,
> I think that would make it available in Express late
> this year.
Is there a specific Nevada build you are going to target? I'd love to
start testing this as soon as
> This RFE is also required for crypto support, as the encryption
> algorithm must be known when the filesystem is created.
I'm deeply concerned about this requirement -- in short, basic
principles of crypto hygene require both key and algorithm agility, and
if you can't change this after creatio
Brian Hechinger wrote:
Could you "mix and match" by keeping the current style assuming there
are no -o options present?
# zfs create pool/fs
If you need to specify options, then they should all be options:
# zfs create -o name=pool/fs -o mountpoint=/bar -o etc
I would be tempted to have two
On August 15, 2006 12:03:17 PM -0500 David Dyer-Bennet <[EMAIL PROTECTED]>
wrote:
On 8/15/06, Richard Elling - PAE <[EMAIL PROTECTED]> wrote:
This can be configured with the local mail delivery agent. You could even
put incoming mail in someone's $HOME, however that isn't always a good idea.
On 8/15/06, Richard Elling - PAE <[EMAIL PROTECTED]> wrote:
This can be configured with the local mail delivery agent. You could even
put incoming mail in someone's $HOME, however that isn't always a good idea.
I've run across systems that don't deliver into $HOME, and it always
ends up leadi
Anton B. Rang wrote:
One problem with this approach is that software expects /var/mail to be full of files,
not directories, for each user. I don't think you can get the right semantics out of
ZFS for this yet (loopback mounting a file comes to mind, but breaks down if something
tries to delet
Hello All,
Here is customer's reply:
I guess since the zones we are working with
are running /acting as Oracle 10 database
servers, the 100% memory usage prstat is not
accurate. Also, from the text below it seems
that rcapd is not the way to go to segregate
memory in zones and to wait for LDOMs w
One problem with this approach is that software expects /var/mail to be full of
files, not directories, for each user. I don't think you can get the right
semantics out of ZFS for this yet (loopback mounting a file comes to mind, but
breaks down if something tries to delete the user's mailbox w
I would suggest taking a version of approach (1), myself.
Rather than special-casing ZFS, we could issue a VOP_CROSS_RENAME (or some such
call) if the source and destination directory were on different file systems
implemented by the same filesystem module. If this returned failure (e.g. the
EN
Jeremy Teo wrote:
Hello,
this is with reference to bug #6343653, "want to quickly "copy" a file
from a snapshot".
After a short dig through source code, the issue is that 'mv' will do
a copy because the rename syscall fails for files on different
filesystems (snapshots are mounted as separate f
Hello,
this is with reference to bug #6343653, "want to quickly "copy" a file
from a snapshot".
After a short dig through source code, the issue is that 'mv' will do
a copy because the rename syscall fails for files on different
filesystems (snapshots are mounted as separate filesystems from the
On Tue, Aug 15, 2006 at 08:56:00PM +0930, Darren J Moffat wrote:
> Eric Schrock wrote:
>
> >This case adds a new option, 'zfs create -o', which allows for any ZFS
> >property to be set at creation time. Multiple '-o' options can appear
> >in the same subcommand. Specifying the same property mult
> The other filesystem is /var/mail on my mail server.
> I've traditionally
> un (big) user quotas in mailboxes just to keep some
> malicious
> emailer from filling up /var/mail, maybe. The
> notion of having
> one zfs filesystem per mailbox seems unwieldy, just
> to run quotas
> per user.
It s
32 matches
Mail list logo
