> And, like it or not, LDL has a "funky special first track" too.
That is not correct.
> Root file system on an LV is anathema to me and the other people
> that have been burned by it.
My experience with root FS in LV is recent. Love it!
My embracing of LVM (before root) happened slo
> If the user knew that they
> intend to format a disk with potentially unsafe data on it they could just
> bring
> it online unformatted. (By unsafe I mean data that may be partially in a good
> format and partially in bad).
Or you could configure your directory manager to erase on deallocate (o
>>> On 3/14/2013 at 02:45 PM, Rick Troth wrote:
-snip-
> Specially sized minidisks are not the only option. Think LVM.
> If you're trying to get free from the battle of wasted space versus
> wasted time and effort, logical volumes work really well. Nothing
> else in Linux land comes close.
If
On 3/14/2013 at 11:25 AM, Rick Troth wrote:
>> THE ONLY time Linux actually *needs* CDL is when the disk will be
>> shared with MVS.
On Thu, Mar 14, 2013 at 1:26 PM, Mark Post wrote:
> Perhaps in a z/VM environment, but that's not completely true even there.
> The ability to create multiple
> Maybe a requirement that ICKDSF (as if it wern't complicated enough now)
> support LINUX initialization (formatting).
Somehow I doubt that would happen.
Knowing a little bit more about what Tomas is trying to do, he's trying to
avoid waiting for a long format to complete, so he doesn't want t
>>> On 3/14/2013 at 12:07 PM, "Pavelka, Tomas" wrote:
> If there was a way to tell the kernel to bring the device online without the
> analysis, the problem would be solved.
File a requirement with IBM. That's the only way that's going to happen.
Mark Post
--
>>> On 3/14/2013 at 11:25 AM, Rick Troth wrote:
> THE ONLY time Linux actually *needs* CDL is when the disk will be
> shared with MVS.
Perhaps in a z/VM environment, but that's not completely true even there. The
ability to create multiple partitions with CDL is very useful. Not _having_ to
> One error message is ignorable. Hundreds are a problem that should be
> fixed.
I just had to learn this the hard way... I started playing with
raw_track_access, noticed the large number of I/O errors reported, but paid it
no mind and made it work. I wrote a CKD track that was not recognized a
Maybe a requirement that ICKDSF (as if it wern't complicated enough now)
support LINUX initialization (formatting).
On Thu, Mar 14, 2013 at 8:17 AM, David Boyes wrote:
> > > Please ignore the few Buffer I/O errors in syslog.
>
> One error message is ignorable. Hundreds are a problem that should
On Wed, Mar 13, 2013 at 4:04 PM, Mark Post wrote:
...
> I think the best method is to CPFMTXA at _least_ cylinder 0
> before giving it to a guest. It really should be the entire volume,
> or use the DIRMAINT function to erase things for you.
I mostly agree with Mark: clip the disk, so to sp
> > Please ignore the few Buffer I/O errors in syslog.
One error message is ignorable. Hundreds are a problem that should be fixed.
> I think
> the best method is to CPFMTXA at _least_ cylinder 0 before giving it to a
> guest. It really should be the entire volume, or use the DIRMAINT function
>
Behalf Of Mark Post
Sent: Wednesday, March 13, 2013 9:05 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DASD format from Linux only
>>> On 3/13/2013 at 12:20 PM, Stefan Haberland wrote:
> Hi Tomas,
>
> I have a possible solution for you from within Linux. You can set the
>
gt; Sent: Wednesday, March 13, 2013 01:59
> To: LINUX-390@vm.marist.edu
> Subject: Re: DASD format from Linux only
>
> Thanks for the replies, here are my thoughts on the problem:
>
> I agree that before a minidisk is given to a guest (before the guest is
> started for the fir
s web site.
Dennis O'Brien
Wanted, Dead and Alive: Schrödinger's Cat
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of Pavelka,
Tomas
Sent: Wednesday, March 13, 2013 01:59
To: LINUX-390@vm.marist.edu
Subject:
>>> On 3/13/2013 at 12:20 PM, Stefan Haberland wrote:
> Hi Tomas,
>
> I have a possible solution for you from within Linux. You can set the
> device online with raw_track_access enabled.
>
> $ echo 1 > /sys/bus/ccw/devices/0.0./raw_track_access
> $ chccwdev -e
>
> Please ignore the fe
aw those errors even when running normal dasdfmt so
this is nothing new.
Tomas
-Original Message-
From: Stefan Haberland [mailto:s...@linux.vnet.ibm.com]
Sent: Wednesday, March 13, 2013 5:20 PM
To: Linux on 390 Port
Cc: Pavelka, Tomas
Subject: Re: DASD format from Linux only
Hi Tomas,
I
Hi Tomas,
I have a possible solution for you from within Linux. You can set the
device online with raw_track_access enabled.
$ echo 1 > /sys/bus/ccw/devices/0.0./raw_track_access
$ chccwdev -e
Please ignore the few Buffer I/O errors in syslog.
Afterwards you can format the device usin
Here is another possibility.
As in your possibility number 1 write a CMS format on every new disk.
Then run CMS2CDL exec which can be downloaded from IBM's VM download page.
The CMS2CDL runs very quickly, it only writes a CDL VTOC with LINUX
partition information.
CMS2CDL first checks that the disk
Thanks for the replies, here are my thoughts on the problem:
I agree that before a minidisk is given to a guest (before the guest is started
for the first time) the minidisk needs to be formatted and any data that was
previously on the disk erased. The question is, when to do it and from which O
> Excuse my ignorance, but what is "FBAF"?
This is a minidisk definition in the user directory:
MDISK FBAF 3390 4819 1000 VMBL2H WR
FBAF is the virtual address of the disk.
When we first ran into this, we were doing experiments and weren't sure if we
are able to reproduce the problem. But we had
Its one of those funny FBA devices that live on a 3390.
On Tue, Mar 12, 2013 at 3:20 PM, Tom Huegel wrote:
> Now I feel stupid .. I was looking at the type FBA-512 and was off thinking
> FBA(F=format??) I am going to blame it on the new dog, he kept me up all
> night with his wimpering..
>
> On
Now I feel stupid .. I was looking at the type FBA-512 and was off thinking
FBA(F=format??) I am going to blame it on the new dog, he kept me up all
night with his wimpering..
On Tue, Mar 12, 2013 at 11:51 AM, Mark Post wrote:
> >>> On 3/12/2013 at 02:45 PM, Tom Huegel wrote:
> > Excuse my igno
>>> On 3/12/2013 at 02:51 PM, James Tison wrote:
> FBAF = Fixed Block Architecture Format
Not in the context of an MDISK statement.
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to l
FBAF = Fixed Block Architecture Format
Regards,
--Jim--
--
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/htbi
>>> On 3/12/2013 at 02:45 PM, Tom Huegel wrote:
> Excuse my ignorance, but what is "FBAF"?
>
> On Tue, Mar 12, 2013 at 5:31 AM, Pavelka, Tomas wrote:
>
>> We have been trying to format all minidisks from Linux only and this
>> turned out to be problematic. I am looking for a solution that would
What is "FBAF"? I can't find that reference anywhere.
On Tue, Mar 12, 2013 at 11:28 AM, Alan Altmark wrote:
> On Tuesday, 03/12/2013 at 08:33 EDT, "Pavelka, Tomas"
> wrote:
> > We have been trying to format all minidisks from Linux only and this
> turned out
> > to be problematic. I am looking f
Excuse my ignorance, but what is "FBAF"?
On Tue, Mar 12, 2013 at 5:31 AM, Pavelka, Tomas wrote:
> We have been trying to format all minidisks from Linux only and this
> turned out to be problematic. I am looking for a solution that would let us
> stay in Linux without having to involve CMS format
On Tuesday, 03/12/2013 at 08:33 EDT, "Pavelka, Tomas"
wrote:
> We have been trying to format all minidisks from Linux only and this
turned out
> to be problematic. I am looking for a solution that would let us stay in
Linux
> without having to involve CMS format for every new minidisk. Let me
firs
>>> On 3/12/2013 at 08:31 AM, "Pavelka, Tomas" wrote:
> We have been trying to format all minidisks from Linux only and this turned
> out to be problematic. I am looking for a solution that would let us stay in
> Linux without having to involve CMS format for every new minidisk. Let me
> first
We have been trying to format all minidisks from Linux only and this turned out
to be problematic. I am looking for a solution that would let us stay in Linux
without having to involve CMS format for every new minidisk. Let me first
describe the problem:
When there is a record on dasd that has i
30 matches
Mail list logo
