Mark,
> With btrfs now the default file system on sles12, is there a new
> recommended way to layout DASD devices?
Good question.
I have also been thinking of the Copy On Write (COW) feature. So a
follow-up question might be: "How do I utilize the cloning and COW features
of btrfs?" .
With containers in vogue lately, I could imagine one Linux system with a
btrfs file system in a virtual machine. Then, for similar workloads,
containers with clones of that root file system could be created. Each
container should require very little additional disk space. If there were
sizable data associated with each workload, that could be stored in
separately mounted file systems. And when you patch that Linux, you've just
patched all the "container-clones".
The devil is in the details.
-Mike MacIsaac
On Wed, Dec 17, 2014 at 9:41 AM, Mark Pace <[email protected]> wrote:
>
> With btrfs now the default file system on sles12, is there a new
> recommended way to layout DASD devices?
> I would think if you had really big 3390 devices that btrfs makes sense.
> But still working with mod-9s it doesn't seem like the right fit.
>
> I'm still putting / on a minidisk and then creating a large LVM and
> breaking out
> home
> srv
> tmp
> usr
> var
> opt
> into logical volumes in the LVM.
>
> On Wed, Nov 19, 2014 at 4:08 PM, Mark Post <[email protected]> wrote:
> >
> > >>> On 11/19/2014 at 07:43 AM, "Levy, Alan" <[email protected]> wrote:
> > > During the install, I removed /var, /opt/ ,tmp and /home from the btrfs
> > > (dasda). I then created these partitions on their own device (dasdb
> thru
> > > dasde). When I log in, via maintenance mode due to the failed
> dependency
> > > errors, everything looks fine. I can see the separated partitions. I
> can
> > > create files/directories within those mount points. The /etc/fstab
> looks
> > ok
> > > also. This looks like some kind of timing issue.
> >
> > Sounds like a support request is the way to go here. But, before you do,
> > check to see if any maintenance is available. Bug fixes for SLE12 are
> > going out the door all the time.
> >
> >
> > Mark Post
> >
> > ----------------------------------------------------------------------
> > For LINUX-390 subscribe / signoff / archive access instructions,
> > send email to [email protected] with the message: INFO LINUX-390 or
> > visit
> > http://www.marist.edu/htbin/wlvindex?LINUX-390
> > ----------------------------------------------------------------------
> > For more information on Linux on System z, visit
> > http://wiki.linuxvm.org/
> >
>
>
> --
> The postings on this site are my own and don’t necessarily represent
> Mainline’s positions or opinions
>
> Mark D Pace
> Senior Systems Engineer
> Mainline Information Systems
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> ----------------------------------------------------------------------
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
