Hi List,
When I run mksles9root.sh I encounter this problem :
# ./mksles9root.sh s390x -m
Making a SLES9 install tree ...
SP4 ISO images found ...
The tree named sles9xsp4root/ will be SLES9 + SP4 ...
Making the directory structure ...
Mounting ISO images loopback ...
Mounting
Bernard,
So you have 16 loopback devices. But I see the error:
mount: could not find any free loop device
So I wonder how many of the 16 are available for use. What does mount |
grep loop return? (I'm not sure of another way of telling which loopback
devices are being used). Here's an example:
Hi Mike,
I did a fuser /dev/loop? on all 16 and it came back clean.
However , the mount | greep loop produced this :
# mount | grep loop
/nfs/iso/SLES-10-SP2-DVD-s390x-GM-DVD1.iso on /nfs/sles10sp2/dvd1 type
iso9660 (rw,loop=/dev/loop0)
df -h shows :
On Tuesday 28 October 2008 09:25, Bernard Wu wrote:
Hi List,
When I run mksles9root.sh I encounter this problem :
...
Mounting SLES9 SP4 ISO images loopback ...
Mounting sles9xsp4root/sp4/CD1/ ...
Mounting sles9xsp4root/sp4/CD2/ ...
mount: could not find any free loop device
Cleaning up mount
Thanks Ed,
But losetup -a comes up empty handed.
So does fuser /dev/loop? on all 16 devices.
The information contained in this e-mail message is intended only for
the personal and confidential use of the recipient(s) named above. This
message may be an attorney-client communication and/or work
All of the documentation that I have found indicates that the DB2
Application Development Client needs to be installed before php can be
built with Db2 support. I am struggling to get the development client
installed because it is in rpm format and my Slack system does not use
rpm's. Can anyone
But losetup -a comes up empty handed.
Hmm, you were showing at least /dev/loop0 being used earlier.
Try making 6 mount points and mounting the 6 ISO images manually. If this
fails then something may be wrong with you loopback devices. If it
succeeds then something may be wrong with the script.
OK. Looks like something is wrong with the devices. I tried it manually
and this is what I got :
***796*** [EMAIL PROTECTED]:/nfs/iso] *** uid=0 ***
# mount -o loop,ro SLES-9-s390x-RC5a-CD1.iso sles9xsp4root/sles9/CD1
***797*** [EMAIL PROTECTED]:/nfs/iso] *** uid=0 ***
# mount -o loop,ro
I'm wondering if it's being run as root?
Sent from my iPhone
On Oct 28, 2008, at 8:35 AM, Michael MacIsaac [EMAIL PROTECTED]
wrote:
But losetup -a comes up empty handed.
Hmm, you were showing at least /dev/loop0 being used earlier.
Try making 6 mount points and mounting the 6 ISO images
I'm wondering if it's being run as root?
Yes, the script is run by root.
The information contained in this e-mail message is intended only for
the personal and confidential use of the recipient(s) named above. This
message may be an attorney-client communication and/or work product and
as such
On Oct 28, 2008, at 10:07 AM, Bernard Wu wrote:
OK. Looks like something is wrong with the devices. I tried it
manually
and this is what I got :
# mount -o loop,ro SLES-9-SP4-CD-s390x-RC7-CD3.iso sles9xsp4root/sp4/
CD3
mount: could not find any free loop device
Maximum of 8 loop devices.
Hello!
Russ, typically Slack contains a command to translate those RPM files into
TGZ ones. Look for the rpm2tgz command, and follow its instructions.
As for your question regarding PHP and DB2, on that issue I'm not sure. I do
know that PHP does support the MySQL database product.
--
Gregg C
I noticed in your earlier post that mount | grep loop showed a DVD iso
mounted on loop0 -- but your losetup -a shows loop0 being mounted as the CD1
iso ..Have you tried umounting the DVD iso? It looks like an NFS mount
..
Just wondering if something is mucked up -- what does df -h show
Thanks Adam,
Add options loop max_loop=64 (or up to 255, I think) in /etc/
modules.conf
But there is no /etc/modules.conf .
There is a modprobe.conf and a modprobe.conf.local. A grep of loop on
modprobe.conf shows :
alias block-major-7 loop
Maybe this explains why it fails when I try to
On Tuesday 28 October 2008 11:14, Adam Thornton wrote:
Maximum of 8 loop devices.
Easy to fix.
Add options loop max_loop=64 (or up to 255, I think) in /etc/
modules.conf.
You will need to rmmod and then modprobe loop again, so it may be
simpler just to reboot.
Or, change max_loop and manually
On Tuesday 28 October 2008 11:57, Bernard Wu wrote:
But there is no /etc/modules.conf .
There is a modprobe.conf and a modprobe.conf.local. A grep of loop on
modprobe.conf shows :
alias block-major-7 loop
Maybe this explains why it fails when I try to mount loop8.
Nope. That 7 is the
This is what I got from IBM support.
In the 2.6 kernel for SLES 9, the loop module has been compiled into the
kernel. You will need to edit your /etc/zipl.conf and add the following:
max_loop=16
Then run zipl
Then reboot.
That fixed it.
Thanks to all who replied.
Bernie Wu
The information
17 matches
Mail list logo
