CAVMEN Meeting on Thursday, June 18, 2009 - Agenda Update

2009-06-08 Thread Chicago Area VM (and Linux) Enthusiasts
Meeting Agenda Change: A third afternoon session has been added. The session start times have changed. Please read carefully. The third quarter meeting of the Chicago Area VM (and Linux) Enthusiasts will be held on Thursday, June 18, 2009. -- Meeting Location: This quarter's

Re: Mounting a filesystem *really* read-only

2009-06-08 Thread Carsten Otte
Am Fri, 5 Jun 2009 16:47:15 -0700 schrieb Ted Rodriguez-Bell te...@wellsfargo.com: Now I think we could work around this by changing the device to read-only before mounting, so you'd do something like this: blockdev --setro /dev/dasdXX # Lock the device if mount /dev/dasdXX

Re: Mounting a filesystem *really* read-only

2009-06-08 Thread van Sleeuwen, Berry
Be aware that if you do use reserve/release you *MUST* set the DASD to shared if you are running in multiple VM's. At the very least the one where you put the lock file. If you don't you will get problems with locking DASD devices. As we experienced with our VSE systems a few years back. One of 4

Re: CAVMEN Meeting on Thursday, June 18, 2009 - Agenda Update

2009-06-08 Thread Ron Wells
Is there a group around So.Indiana area.. From: Chicago Area VM (and Linux) Enthusiasts cav...@comcast.net To: LINUX-390@VM.MARIST.EDU Date: 06/08/2009 01:38 AM Subject: CAVMEN Meeting on Thursday, June 18, 2009 - Agenda Update Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU Meeting

Re: CAVMEN Meeting on Thursday, June 18, 2009 - Agenda Update

2009-06-08 Thread Alan Altmark
On Monday, 06/08/2009 at 08:50 EDT, Ron Wells rwe...@agfinance.com wrote: Is there a group around So.Indiana area.. http://www.vm.ibm.com/events/usergrps.html contains the list we know about. You are sitting between CAVMEN (Chicago) and MVMRUG (Columbus, OH). A few years ago I spoke at an

Re: Mounting a filesystem *really* read-only

2009-06-08 Thread Alan Altmark
On Monday, 06/08/2009 at 05:09 EDT, van Sleeuwen, Berry berry.vansleeu...@atosorigin.com wrote: Be aware that if you do use reserve/release you *MUST* set the DASD to shared if you are running in multiple VM's. Reminder of cross-system Reserve/Release requirements for minidisks: - Must be a

Re: CAVMEN Meeting on Thursday, June 18, 2009 - Agenda Update

2009-06-08 Thread Ron Wells
Alan Thanks for ref... we are south 7hrs from Chicago and 5 to Ohio ...approx... still see nothing close by.. but still hoping a group may form around area ... From: Alan Altmark alan_altm...@us.ibm.com To: LINUX-390@VM.MARIST.EDU Date: 06/08/2009 08:24 AM Subject: Re: CAVMEN Meeting on

Re: CAVMEN Meeting on Thursday, June 18, 2009 - Agenda Update

2009-06-08 Thread Melancon, Ruddy
I looked at the list of user groups on the web site. I did not see any located in the south [Louisiana, Mississippi, Alabama, Georgia]. Has anyone ever tried to start a VM/Linux User Group in the south? Ruddy A. Melancon IT Systems Specialist, Senior Alabama Department of Transportation

Re: CAVMEN Meeting on Thursday, June 18, 2009 - Agenda Update

2009-06-08 Thread Shawn Wells
There is one in Atlanta -- the Atlanta System z Linux Council. I'm not aware of a formal webpage for it, but Carlos Torres carlost[at]us.ibm.com of IBM runs the show. If you ping him, I'm sure you can get on meeting notices. Melancon, Ruddy wrote: I looked at the list of user groups on the

MIDAWs support and SLES9 SLES10 under z/VM 5.3

2009-06-08 Thread Shedlock, George
I am sending this for a friend who seems to be having difficulty posting it himself. We are looking at activating MIDAWs support on one of our disk subsystems. The disk subsystem is split between z/OS and z/VM (5.3 RSU 0802). I see that z/VM support MIDAWs for guest operating systems. My

Re: Mounting a filesystem *really* read-only

2009-06-08 Thread Marcy Cortes
You forgot one :) - Must not use GDPS Hyperswap. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any

Re: CAVMEN Meeting on Thursday, June 18, 2009 - Agenda Update

2009-06-08 Thread Alan Altmark
On Monday, 06/08/2009 at 10:27 EDT, Shawn Wells swe...@redhat.com wrote: There is one in Atlanta -- the Atlanta System z Linux Council. I'm not aware of a formal webpage for it, but Carlos Torres carlost[at]us.ibm.com of IBM runs the show. If you ping him, I'm sure you can get on meeting

Re: CAVMEN Meeting on Thursday, June 18, 2009 - Agenda Update

2009-06-08 Thread Ron Wells
Thanks Shawn will look into it From: Shawn Wells swe...@redhat.com To: LINUX-390@VM.MARIST.EDU Date: 06/08/2009 09:26 AM Subject: Re: CAVMEN Meeting on Thursday, June 18, 2009 - Agenda Update Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU There is one in Atlanta -- the Atlanta System z

Re: CAVMEN Meeting on Thursday, June 18, 2009 - Agenda Update

2009-06-08 Thread Ron Wells
We are Ky/So.Ill /So.Ind area. From: Melancon, Ruddy melanc...@dot.state.al.us To: LINUX-390@VM.MARIST.EDU Date: 06/08/2009 09:17 AM Subject: Re: CAVMEN Meeting on Thursday, June 18, 2009 - Agenda Update Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU I looked at the list of user groups

Re: CAVMEN Meeting on Thursday, June 18, 2009 - Agenda Update

2009-06-08 Thread David Boyes
There is one in Atlanta -- the Atlanta System z Linux Council. Yes, they just met on Friday, in fact. Pretty good attendance as well -- 40+ people. Pretty much all it takes to start a user group is some interest, somewhere to meet, a box of donuts and a bucket of coffee from your local

Re: CAVMEN Meeting on Thursday, June 18, 2009 - Agenda Update

2009-06-08 Thread David Boyes
We are Ky/So.Ill /So.Ind area. I wonder if UKy would spare you a classroom for a day? They did a bang-up job when they hosted VM Workshop long ago. IUPUI or Purdue might be other options if they're still IBM customers. --

Re: CAVMEN Meeting on Thursday, June 18, 2009 - Agenda Update

2009-06-08 Thread Ron Wells
Alan Just sent Carlos an email...see what he says.. From: Alan Altmark alan_altm...@us.ibm.com To: LINUX-390@VM.MARIST.EDU Date: 06/08/2009 09:34 AM Subject: Re: CAVMEN Meeting on Thursday, June 18, 2009 - Agenda Update Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU On Monday,

subscribe

2009-06-08 Thread D Waldo Anderson
dwaldoanderson -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 image001.gif

Re: Mounting a filesystem *really* read-only

2009-06-08 Thread Shane Ginnane
If the access will truly be read-only, then mount the file system as ext2, and not ext3. I don't believe that will work if the dirty flag is on - which it will be if you are worried about journal replay on (re-)mount. Shane ...

Re: Mounting a filesystem *really* read-only

2009-06-08 Thread Mark Post
On 6/8/2009 at 7:38 PM, Shane Ginnane sginn...@isi.com.au wrote: If the access will truly be read-only, then mount the file system as ext2, and not ext3. I don't believe that will work if the dirty flag is on - which it will be if you are worried about journal replay on (re-)mount. It

Re: Mounting a filesystem *really* read-only

2009-06-08 Thread Ivan Warren
Ted Rodriguez-Bell wrote: The first thing we tried was just to have B mount the disks read-only and check for a flag file; if that file (we'll call it IN_USE) exists, don't do anything. If it doesn't, then A has shut down nicely and it's safe to grab the filesystem read-only. Hrmm... Wait a

Re: Mounting a filesystem *really* read-only

2009-06-08 Thread Mark Post
On 6/8/2009 at 8:02 PM, Ivan Warren i...@vmfacility.fr wrote: Second (as Mark noted) - you may think you can mount the FS R/O and prevent the log from being replayed by specifying you want a non-journaled FS (aka EXT2) - which may (and will) lead to the FS being marked dirty (as Shane

Re: Mounting a filesystem *really* read-only

2009-06-08 Thread Shane Ginnane
Mark wrote on 09/06/2009 11:02:22 AM: Second (as Mark noted) - you may think you can mount the FS R/O and prevent the log from being replayed by specifying you want a non-journaled FS (aka EXT2) - which may (and will) lead to the FS being marked dirty (as Shane noted) - requiring a 'fsck'

Re: Mounting a filesystem *really* read-only

2009-06-08 Thread Mark Post
On 6/8/2009 at 11:18 PM, Shane Ginnane sginn...@isi.com.au wrote: -snip- If you attempt to mount a *clean* ext3 f/s as ext2 you get the warning - and a successful mount. With a dirty journal it refuses to mount as ext2 (ro *or* rw). So, make the file system really be ext2, and not ext3. If