upgrade to SP2 on SLES-11
>>> On 7/18/2012 at 02:12 PM, Pedro Principeza wrote:
> I believe you should not use /dev/dasdX naming. Instead, map
> /etc/fstab entries to /dev/disk/by-id.
As Mauro suggested, /dev/disk/by-path/ is preferable, since by-id can change if
your disks get
>>> On 7/18/2012 at 02:12 PM, Pedro Principeza wrote:
> I believe you should not use /dev/dasdX naming. Instead, map /etc/fstab
> entries to /dev/disk/by-id.
As Mauro suggested, /dev/disk/by-path/ is preferable, since by-id can change if
your disks get moved to a new storage array by the stora
> I've adopted this in my environment but I'm seeing inconsistent naming for
> the partition when Linux boots. This is SLES11-SP1. When SLES comes up, the
> /dev/dasd name will vary from boot to boot. This makes it hard to reference
> the name is fstab because it keeps changing.
Use the by-path na
Just reference it by path:
/dev/disk/by-path/ccw-0.0.0300
The path will never change by itself, but the name does.
Em 18/07/2012 14:11, "KEETON Dave * ETS" escreveu:
> I'm going to piggy-back on this thread because my question is directly
> related to SWAPGEN.
>
> I've adopted this in my environ
Hi.
I believe you should not use /dev/dasdX naming. Instead, map /etc/fstab
entries to /dev/disk/by-id.
HTH,
Pedro Principeza
From: KEETON Dave * ETS
To: LINUX-390@vm.marist.edu,
Date: 18/07/2012 15:09
Subject:Re: SWAPGEN problem after upgrade to SP2 on SLES-11
Sent by
I'm going to piggy-back on this thread because my question is directly related
to SWAPGEN.
I've adopted this in my environment but I'm seeing inconsistent naming for the
partition when Linux boots. This is SLES11-SP1. When SLES comes up, the
/dev/dasd name will vary from boot to boot. This mak
> Our workaround was to change SWAPGEN to reduce the page count in the
> signature page by one, and to increase the minimum number of allocation
> blocks by 8, i.e., 4096/512.
>
> I've sent a copy of our updated SWAPGEN to Dave Jones.
And Jim's fix is now integrated into the mainline SWAPGEN dist
We ran into this as soon as we tried SLES11 SP2.
From previous comments, it appears that the problem is sensitive to
the specific number of 512-byte VDISK allocation blocks requested,
so some people run into it and others don't. In our case, the
wrapper EXEC that we used to invoke SWAPGEN resulte
my 2cents
From: Mark Post
To: LINUX-390@VM.MARIST.EDU,
Date: 06/13/2012 06:44 PM
Subject: Re: SWAPGEN problem after upgrade to SP2 on SLES-11
Sent by:Linux on 390 Port
Further investigation reveals that the problem is size-related (somehow).
If I use this command:
swapgen
I dumped the contents of the swap spaces, at 100K 512 byte sectors and at 200K
512 byte sectors, using both SWAPGEN and mkswap to create them. The
differences in output is interesting, but I can't say I know what they mean.
--- swapgen.100k.hexdump2012-06-13 18:38:12.0 -0400
+++
Thanks for the suggestion, Mark. To partition or not to partition; that
is the question;-)
I also have another change that would remove the requirement for having
the RXDASD package available as well. If we do need to make a change to
SWAPGEN, I'll see about adding that in as well.
DJ
On 06/
Further investigation reveals that the problem is size-related (somehow). If I
use this command:
swapgen 300 10 (diag
the the swapon command fails. (And I do mean fails, and not just seemingly so.
No swap is added.)
If I use this command:
swapgen 300 20 (diag
Then the swapon command w
>>> On 6/13/2012 at 05:50 PM, Mark Post wrote:
> On SLES11 SP1, "swapon -v" shows the same complaint as on SP2, but the swap
> space is added anyway.
It turns out that on SLES11 SP2, the swap space also gets added, in spite of
the message. So it appears that the difference between SP1 and SP2
>>> On 6/13/2012 at 05:02 PM, David Boyes wrote:
> We're looking at it too. More if we find something.
If modifications become necessary (for whatever reason), it might be a good
idea to change something else as well. For DIAG, SWAPGEN puts the swap
signature at the beginning of the first p
Interesting. On SLES10 SP4 and SLES11 SP1 the swapon command works without
complaint. On SLES10 SP4, the "swap -v" command doesn't produce any more
output than without the -v. On SLES11 SP1, "swapon -v" shows the same
complaint as on SP2, but the swap space is added anyway.
On SLES11 SP2, us
Aria,
I ran into this writing the last cookbook. I found this e-mail when
someone in Boeb. debugged it:
I tried to compare the messages from the two scenarios (with and without
SWPAGEN). This is what I found.
With SWAPGEN the amount of swap space detected by Linux is as follows:
Adding 2
>>> On 6/13/2012 at 04:43 PM, Dave Jones wrote:
> Yes, Rich Smrcina has reported this problem as well. To the best of my
> knowledge, the 2008-04-16 version of SWAPGEN is the latest. If the fix
> for this problem has already been discovered, please let me know so I
> can add it into the "official
> Due to kernel rebase of SLES11 SP2 we found that few of the tools that
> earlier worked with
> SLES11 SP2 (2.6.32 based kernels) had to be modified so that they work with
> 3.x kernels.
> SWAPGEN might as well be another such example which might need
> modification to work with 3.x based kernels.
Hi, Mike.
Yes, Rich Smrcina has reported this problem as well. To the best of my
knowledge, the 2008-04-16 version of SWAPGEN is the latest. If the fix
for this problem has already been discovered, please let me know so I
can add it into the "official" SWAPGEN distribution code at SNA.
Thanks.
D
I've seen this on SLES11-SP2 too... And I saw some other issues with
SP2, like not arp-ing when bringing a interface online, and hanging
the ssh terminal on exit...
I've solved the problem with a script, running after all services. The
script does the mkswap and swapon on them. And works.
Mauro
h
>>> On 6/13/2012 at 02:35 PM, Aria Bamdad wrote:
> swapon on /dev/dasdc1
>
> swapon: /dev/dasdc1: found swap signature: version 1, page-size 4, same byte
> order
>
> swapon: /dev/dasdc1: pagesize=4096, swapsize=66547712, devsize=66547200
>
> swapon: /dev/dasdc1: last_page 0x03f77000 is larger
Hi,
I have found a problem with SWAPGEN once I upgraded to SLES11-sp2. I have
no problem with it working on previous including SP1) versions of SLES but
once I upgraded to SP2, I start seeing the following message at Linux boot:
Swap area shorter than signature indicates
Needless to say, t
22 matches
Mail list logo
