base60 wrote:
> StephenRichter@gmail.com wrote:
> > Are there significant differences between the LVM of AIX and Linux?
>
> Vendors copyright their source code so, yeah, they're different.
>
> > Also, what is the release history of this feature of the OS? I am new
> > to UNIX of all stripes, running AIX 5.3 on an ebay 170 44P. The LVM is
> > looking like the first big issue to tackle when learning AIX/Linux.
>
> No, the first big issue is doing a bit of research... books, faq etc
> rather than posting this sort of question.

suit yourself. I answer a lot of questions on line and never give this
kind of response. Just dont think you have to give a comprehensive
answer and you should be fine.

regarding books on AIX, etc. The only IBM redbook on AIX LVM is dated
2000. The AIX 5L admin book by Randall Michael I have is copyright
2002. ( that is why I was thinking the Linux LVM and AIX version came
out around the same time. ) I have been at this a week or two and see
two AIX books on Amazon, no non IBM web site dedicated to AIX. The IBM
site is ok but it does not put its info in context.

Learning AIX is doable. The archives of this NG that I access thru
google groups is the best resource. The issue when I search here is
that a lot of hits refer back to posts in the 1990s. So I dont know
what is relevent and what is not.

> >
> > Did the LVM in Linux and AIX come out around the year 2000 or so? If
> > so, any major changes since then?
>
> Re-read above.
>
> JFS has been on AIX since inception.
>
> >
> > If the LVM of Linux and AIX did come out around the same time, why the
> > difference in terminology? In Linux you have physical extents vs AIX
> > physical partitions? To grow a logical volume in Linux you "lvextend".
> > Not the same in AIX?
>
> Re-read above & copyright comment.
>
> >
> > I am looking to automate the allocation of space as much as possible. I
> > am an AS400 refugee where OS400 handles all of this automatically. I
> > like the flexibility of the LVM approach but would like the ability to
> > put the system on auto pilot also.
>
> Which may work until the first time you have a process run-away and it
> sucks every bit of available disk space.

in OS400 you set a size limit at the file level. The OS400 library,
which is roughly equivalent to the UNIX file system, has no size
limits. The size limit of the files ( we are talking database files )
is set to a number of rows. You can set the limit to *nomax or a
number of rows you know the file/table will never grow to. The default
for a new table might be 30,000 rows. When you hit the limit the job
stops, an inquiry message is sent to the QSYSOPR message queue, and you
can respond to cancel the job or increase the size limit and the job
continues on its merry way. Works very well. I have never seen an
as400 system crash because of a run away job. They do run out of
space, but that is because idiot IBM prices i5 hardware and i5/OS
software at such a premium that users often are running on undersized
systems. I drool when I visit the IBM p5 site and see the quad core
systems selling at market prices. A quad core i5 will be priced at mid
6 figures easy.

>
> There are lots of good reasons to put limits on things.
>
> Rather than looking for a panacea for an OS switch, start reading.

WIll do. Appreciate any help I get.

-Steve