William L. Thomson Jr. wrote: > On Sat, 2011-04-02 at 19:49 -0400, Kyle Gonzales wrote: >> R P Herrold wrote: > >>> A cautious sysadmin may decide it is more important to be able to access >>> the (usually static linked) content in /bin/ and /sbin/ without needing >>> to get the LVM up and running first. As floppy and CD drives are >>> increasingly a rarity on server grade hardware, this seems reasonable, >>> as accessing a rescue image 'across the wire' is fairly challenging, as >>> it is not often done by most admins >> I call BS on that. In fact, my previous email told you exactly how >> sysadmins do make a rescue environment easily available to their servers >> using the available hardware features. > > Let us know when you are said system admin faced with such a problem. Or > you can listen to people who have been there and done that. Your call > either way :)
I've been that sysadmin. I've managed more systems on more continents than you have, with more revenue and more at stake when my systems went down. You really do not want to play that card. But hey, when you have responsibility for 15 locations on 4 continents, running the back office and networking for a major technology corporation, let's talk. > I am smelling allot of sales BS just the same.... I am smelling alot of developer playing sysadmin with his small environment just the same... >>> I speak here, 'wearing the tee-shirt', having spent time doing just such >>> a recovery where a end customer took the Red Hat approach as to LVM'ing, >>> and ended up with a non-bootable system -- the hardware had a >>> motherboard from Intel, calling for a hardware raid driver, 'not yet in >>> anaconda', and thus not on the rescue disk image either -- anaconda >>> called for the driver disk [it could 'see' no drives until such was >>> used], but that disk was long forgotten, when the recovery was needed >> You are blaming LVM for an issue with the customer's DR planning. > > You have already said RHEL defaults with / on a lvm partition and here > is someone telling you that caused problems. I highly doubt he is lying > about his first hand experience. The problem wasn't LVM. The problem was the user needing a driver disk for their environment, and not having it. "Disk was long forgotten, when the recovery was needed". That is inadequate disaster recovery planning. >> Interesting than that many enterprise environments I see use LVM. > > No one is disputing that LVM is invaluable in enterprise or > non-enterprise environments. But like anything there is a time and place > for its use. It is not a one solution for all things, and that approach > can cause problems. Clearly it has for people, otherwise documents would > not exist suggesting to do things other ways. Much less first hand > experiences with systems that won't boot. It generally causes problems for those who do not know how to use the tools at hand. -- Kyle Gonzales [email protected] GPG Key #0x566B435B Read My Tech Blog: http://techiebloggiethingie.blogspot.com/ --------------------------------------------------------------------- Archive http://marc.info/?l=jaxlug-list&r=1&w=2 RSS Feed http://www.mail-archive.com/[email protected]/maillist.xml Unsubscribe [email protected]
