On Wed, Jun 25, 2008 at 04:41:56PM +1200, Ian Collins wrote:
>
> But with ZFS, the layout is a simple matter of creating filesystems, not
> slicing up drives. The filesystems are in a shared pool, so one doesn't
> have to know how big a particular slice will grow.
Yes, we are agreeing on that par
Brian Hechinger wrote:
> On Tue, Jun 24, 2008 at 04:35:30PM +1200, [EMAIL PROTECTED] wrote:
>> We can only hope that ZFS boot will consign this never ending layout
>> argument to the dust of history.
>>
>
> The layout of disks and filesystems will always be a personal preference
> and will n
On 6/23/08 7:45 PM, "Richard Elling" <[EMAIL PROTECTED]> wrote:
> I think the ability to have different policies for file systems
> is pure goodness -- though you pay for it on the backup/
> restore side.
And another reason why Automated Data Migration is the way to go. "Backup"
and "replication
On Mon, 23 Jun 2008, Richard Elling wrote:
> A side question though, my friends who run Windows,
> Linux, or OSX don't seem to have this bias towards isolating
> /var. Is this a purely Solaris phenomenon? If so, how do we
> fix it?
In addition to the other answers given, I think another reason
On Tue, Jun 24, 2008 at 7:24 AM, Gary Mills <[EMAIL PROTECTED]> wrote:
> On Mon, Jun 23, 2008 at 10:25:09PM -0500, Mike Gerdts wrote:
>>
>> Really it boils down to lots of file systems to hold the OS adds
>> administrative complexity and rarely saves more work than it creates.
>
> Some of us want t
On Tue, Jun 24, 2008 at 04:35:30PM +1200, [EMAIL PROTECTED] wrote:
>
> >On Mon, Jun 23, 2008 at 8:06 PM, Brian Hechinger <[EMAIL PROTECTED]>
> >wrote:
> >>This is not a purely Solaris phenomenon, this is a UNIX phenomenon.
> >>People who run Linux or OSX (I can't speak for Windows users) tend to
On Mon, Jun 23, 2008 at 10:25:09PM -0500, Mike Gerdts wrote:
>
> Really it boils down to lots of file systems to hold the OS adds
> administrative complexity and rarely saves more work than it creates.
Some of us want to use different mount options on /var than on /.
That's why they need to be di
Mike Gerdts writes:
> On Mon, Jun 23, 2008 at 8:06 PM, Brian Hechinger <[EMAIL PROTECTED]> wrote:
>> This is not a purely Solaris phenomenon, this is a UNIX phenomenon.
>> People who run Linux or OSX (I can't speak for Windows users) tend to
>> be "new to the game" and feel that "This 40/80/500GB
On Mon, Jun 23, 2008 at 8:06 PM, Brian Hechinger <[EMAIL PROTECTED]> wrote:
> This is not a purely Solaris phenomenon, this is a UNIX phenomenon.
> People who run Linux or OSX (I can't speak for Windows users) tend to
> be "new to the game" and feel that "This 40/80/500GB disk will never
> fill up"
Maurice Castro wrote:
> Hi All,
> the separating of /var is something that comes from the Unix
> tradition. Much of the Unix tradition of systems administration is
> based on making sure systems with many users remain stable and so
> administrators are prepared to work to make the syste
Hi All,
the separating of /var is something that comes from the Unix
tradition. Much of the Unix tradition of systems administration is
based on making sure systems with many users remain stable and so
administrators are prepared to work to make the system more reliable.
Common Wind
On Mon, Jun 23, 2008 at 05:45:45PM -0700, Richard Elling wrote:
>
> I think the ability to have different policies for file systems
> is pure goodness -- though you pay for it on the backup/
> restore side.
That's a price I for one am willing to pay. ;)
> A side question though, my friends who r
On Mon, Jun 23, 2008 at 8:45 PM, Richard Elling <[EMAIL PROTECTED]>
wrote:
> Brian Hechinger wrote:
> > On Mon, Jun 23, 2008 at 11:18:21AM -0600, Lori Alt wrote:
> >
> >> Sorry it's taken me so long to weigh in on this.
> >>
> >
> > You're busy with important things, we'll forgive you. ;)
> >
> >
Brian Hechinger wrote:
> On Mon, Jun 23, 2008 at 11:18:21AM -0600, Lori Alt wrote:
>
>> Sorry it's taken me so long to weigh in on this.
>>
>
> You're busy with important things, we'll forgive you. ;)
>
>
>> With zfs, we don't actually have to put /var in its own
>> slice. We can achiev
On Mon, Jun 23, 2008 at 11:18:21AM -0600, Lori Alt wrote:
> Sorry it's taken me so long to weigh in on this.
You're busy with important things, we'll forgive you. ;)
> With zfs, we don't actually have to put /var in its own
> slice. We can achieve the same goal by putting it
> in its own dataset
On Mon, Jun 23, 2008 at 4:04 PM, Orvar Korvar
<[EMAIL PROTECTED]> wrote:
> Wouldnt it be nice to break out all file systems in separate zfs file
> systems? Then you could snapshot each file system individually. Just like
> each user has his own filesystem, and I can snapshot that filesystem
> in
Wouldnt it be nice to break out all file systems in separate zfs file systems?
Then you could snapshot each file system individually. Just like each user has
his own filesystem, and I can snapshot that filesystem independently from other
users.
Because of now, if I do a snapshot of /, then ever
Mike Gerdts wrote:
On Wed, Jun 4, 2008 at 11:18 PM, Rich Teer <[EMAIL PROTECTED]> wrote:
Why would one do that? Just keep an eye on the root pool and all is good.
The only good argument I have for separating out some of /var is for
boot environment management. I grew tired of repeati
On Wed, Jun 4, 2008 at 11:18 PM, Rich Teer <[EMAIL PROTECTED]> wrote:
> Why would one do that? Just keep an eye on the root pool and all is good.
The only good argument I have for separating out some of /var is for
boot environment management. I grew tired of repeating my arguments
and suggestio
On Thu, Jun 05, 2008 at 02:30:51PM -0700, Vincent Fox wrote:
> So can I jumpstart and setup the ZFS root config?
>
> Anyone have example profile?
>
See TFM -
http://opensolaris.org/os/community/zfs/boot/zfsbootFAQ/#jumpinstall
has been mentioned in the last day or so on list.
vh
Mads Toftum
--
So can I jumpstart and setup the ZFS root config?
Anyone have example profile?
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Bob Friesenhahn wrote:
> On Thu, 5 Jun 2008, Richard Elling wrote:
>
>
>> Nathan Kroenert wrote:
>>
>>> I'd expect it's the old standard.
>>>
>>> if /var/tmp is filled, and that's part of /, then bad things happen.
>>>
>> Such as? If you find a part of Solaris that cannot deal with
On Thu, 5 Jun 2008, Bob Friesenhahn wrote:
> I expect that it matters when the filesystem gets filled up. The
> functionality offered by /var/run would become quite broken if it was
> full during boot. No nameservice. No daemon PID files. Doors
> broken. Boo-Hoo.
/var/run is memory-reside
On Thu, 5 Jun 2008, Richard Elling wrote:
> Nathan Kroenert wrote:
>> I'd expect it's the old standard.
>>
>> if /var/tmp is filled, and that's part of /, then bad things happen.
>
> Such as? If you find a part of Solaris that cannot deal with a full
> file system, then please (pretty please... w
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Rich Teer
> Sent: Thursday, June 05, 2008 12:19 AM
> To: Bob Friesenhahn
> Cc: ZFS discuss
> Subject: Re: [zfs-discuss] ZFS root finally here in SNV90
>
> On Wed, 4
Nathan Kroenert wrote:
> I'd expect it's the old standard.
>
> if /var/tmp is filled, and that's part of /, then bad things happen.
>
Such as? If you find a part of Solaris that cannot deal with a full
file system, then please (pretty please... with a cherry on top) file a
bug.
> there are of
On Jun 5, 2008, at 5:09 AM, Bob Friesenhahn wrote:
> On Wed, 4 Jun 2008, Henrik Johansson wrote:
>>
>> Anyone knows what the deal with /export/home is? I though /home was
>> the default home directory in Solaris?
>
> It seems that they expect you to use the automounter to mount it.
> That allow
On Thu, 5 Jun 2008, Ellis, Mike wrote:
>
> If SSD is coming fast and furious, being able to use compression, shared
> free-space (quotas etc) to keep the boot-images small enough so they'll
> fit and accommodate live-upgrade patching, will become increasingly
> important.
>
> http://www.networkworl
ginal Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rich Teer
Sent: Thursday, June 05, 2008 12:19 AM
To: Bob Friesenhahn
Cc: ZFS discuss
Subject: Re: [zfs-discuss] ZFS root finally here in SNV90
On Wed, 4 Jun 2008, Bob Friesenhahn wrote:
> Did you actually choos
I'd expect it's the old standard.
if /var/tmp is filled, and that's part of /, then bad things happen.
there are often other places in /var that are writable by more than
root, and always the possibility that something barfs heavily into syslog.
Since the advent of reasonably sized disks, I kno
Rich Teer wrote:
> On Wed, 4 Jun 2008, Bob Friesenhahn wrote
>> Did you actually choose to keep / and /var combined? Is there any
>>
>
> THat's what I'd do...
>
>> reason to do that with a ZFS root since both are sharing the same pool
>> and so there is no longer any disk space advantage
On Wed, 4 Jun 2008, Bob Friesenhahn wrote:
> Did you actually choose to keep / and /var combined? Is there any
THat's what I'd do...
> reason to do that with a ZFS root since both are sharing the same pool
> and so there is no longer any disk space advantage? If / and /var are
> not combine
On Wed, 4 Jun 2008, Henrik Johansson wrote:
>
> Anyone knows what the deal with /export/home is? I though /home was
> the default home directory in Solaris?
It seems that they expect you to use the automounter to mount it.
That allows the same automount map to be used for all systems. It has
be
On Jun 5, 2008, at 12:05 AM, Rich Teer wrote:
> On Wed, 4 Jun 2008, Henrik Johansson wrote:
>
>> Anyone knows what the deal with /export/home is? I though /home was
>> the default home directory in Solaris?
>
> Nope, /export/home has always been the *physical* location for
> users' home directorie
On Wed, 4 Jun 2008, Henrik Johansson wrote:
> Anyone knows what the deal with /export/home is? I though /home was
> the default home directory in Solaris?
Nope, /export/home has always been the *physical* location for
users' home directories. They're usually automounted under /home,
though.
-
Works great! Even tested to create boot environments with live
upgrade, fast, easy and elegant!
Anyone knows what the deal with /export/home is? I though /home was
the default home directory in Solaris?
( I put up some screenshots of the installation process for those
interested: http://s
36 matches
Mail list logo
