Hi!
With yesterday's GIT version of Revisor, I got the following error message:
Downloading Packages: Filesystem label=livecd-20070825 OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 325120 inodes, 649728 blocks 6497 blocks (1.00%) reserved for the super user First data block=0 Maximum filesystem blocks=666894336 20 block groups 32768 blocks per group, 32768 fragments per group 16256 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912
Writing inode tables: Creating journal (16384 blocks): done Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 38 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. tune2fs 1.40.2 (12-Jul-2007) Setting maximal mount count to -1 Setting interval between checks to 0 seconds Cannot setup installation target. Aborting. Do you want to continue? [Y/n] y
What's wrong here, do you think?
Lars
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Lars Bjørndal wrote:
Hi!
With yesterday's GIT version of Revisor, I got the following error message:
Downloading Packages: Filesystem label=livecd-20070825 OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 325120 inodes, 649728 blocks 6497 blocks (1.00%) reserved for the super user First data block=0 Maximum filesystem blocks=666894336 20 block groups 32768 blocks per group, 32768 fragments per group 16256 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912
Writing inode tables: Creating journal (16384 blocks): done Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 38 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. tune2fs 1.40.2 (12-Jul-2007) Setting maximal mount count to -1 Setting interval between checks to 0 seconds Cannot setup installation target. Aborting. Do you want to continue? [Y/n] y
What's wrong here, do you think?
Lars
There was an error in this as I recall, and I was under the impression I got it fixed. I'll test again and come back to this.
- -- Kind regards,
Jeroen van Meeuwen - -kanarip
- -- http://www.kanarip.com/ RHCE, LPIC-2, MCP, CCNA C6B0 7FB4 43E6 CDDA D258 F70B 28DE 9FDA 9342 BF08
On lør, aug 25, 2007 at 03:01:36 +0200, Jeroen van Meeuwen wrote:
Lars Bjørndal wrote:
Hi!
With yesterday's GIT version of Revisor, I got the following error message:
Downloading Packages: Filesystem label=livecd-20070825 OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 325120 inodes, 649728 blocks 6497 blocks (1.00%) reserved for the super user First data block=0 Maximum filesystem blocks=666894336 20 block groups 32768 blocks per group, 32768 fragments per group 16256 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912
Writing inode tables: Creating journal (16384 blocks): done Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 38 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. tune2fs 1.40.2 (12-Jul-2007) Setting maximal mount count to -1 Setting interval between checks to 0 seconds Cannot setup installation target. Aborting. Do you want to continue? [Y/n] y
What's wrong here, do you think?
Lars
There was an error in this as I recall, and I was under the impression I got it fixed. I'll test again and come back to this.
Thank you!
Could it be related to Livecd-tools, and not to Revisor?
Lars
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Lars Bjørndal wrote:
On lør, aug 25, 2007 at 03:01:36 +0200, Jeroen van Meeuwen wrote:
Lars Bjørndal wrote:
Hi!
With yesterday's GIT version of Revisor, I got the following error message:
Downloading Packages: Filesystem label=livecd-20070825 OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 325120 inodes, 649728 blocks 6497 blocks (1.00%) reserved for the super user First data block=0 Maximum filesystem blocks=666894336 20 block groups 32768 blocks per group, 32768 fragments per group 16256 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912
Writing inode tables: Creating journal (16384 blocks): done Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 38 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. tune2fs 1.40.2 (12-Jul-2007) Setting maximal mount count to -1 Setting interval between checks to 0 seconds Cannot setup installation target. Aborting. Do you want to continue? [Y/n] y
What's wrong here, do you think?
Lars
There was an error in this as I recall, and I was under the impression I got it fixed. I'll test again and come back to this.
Thank you!
Could it be related to Livecd-tools, and not to Revisor?
Lars
My guess is the error is in Revisor ;-)
- -- Kind regards,
Jeroen van Meeuwen - -kanarip
- -- http://www.kanarip.com/ RHCE, LPIC-2, MCP, CCNA C6B0 7FB4 43E6 CDDA D258 F70B 28DE 9FDA 9342 BF08
Jeroen van Meeuwen wrote:
Lars Bjørndal wrote:
On lør, aug 25, 2007 at 03:01:36 +0200, Jeroen van Meeuwen wrote:
Lars Bjørndal wrote:
Hi!
With yesterday's GIT version of Revisor, I got the following error message:
Downloading Packages: Filesystem label=livecd-20070825 OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 325120 inodes, 649728 blocks 6497 blocks (1.00%) reserved for the super user First data block=0 Maximum filesystem blocks=666894336 20 block groups 32768 blocks per group, 32768 fragments per group 16256 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912
Writing inode tables: Creating journal (16384 blocks): done Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 38 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. tune2fs 1.40.2 (12-Jul-2007) Setting maximal mount count to -1 Setting interval between checks to 0 seconds Cannot setup installation target. Aborting. Do you want to continue? [Y/n] y
What's wrong here, do you think?
Lars
There was an error in this as I recall, and I was under the impression I got it fixed. I'll test again and come back to this.
I didn't get this error running from either GIT or revisor-2.0.4.3-1rc1 (soon to land in the development repo). Can you reproduce from the latest GIT version?
Kind regards,
Jeroen van Meeuwen -kanarip
On søn, aug 26, 2007 at 12:54:05 +0200, Jeroen van Meeuwen wrote:
I didn't get this error running from either GIT or revisor-2.0.4.3-1rc1 (soon to land in the development repo). Can you reproduce from the latest GIT version?
Yes, I can. I did a new GIT install today, and I got the same error message. Do you need my config files etc.?
I use some files from my own repo, could that be a problem? What does the error message actually indicate?
Lars
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Lars Bjørndal wrote:
On søn, aug 26, 2007 at 12:54:05 +0200, Jeroen van Meeuwen wrote:
I didn't get this error running from either GIT or revisor-2.0.4.3-1rc1 (soon to land in the development repo). Can you reproduce from the latest GIT version?
Yes, I can. I did a new GIT install today, and I got the same error message. Do you need my config files etc.?
I use some files from my own repo, could that be a problem? What does the error message actually indicate?
Lars
Setting up the installation target is merely providing a loopmounted ext3 filesystem. You could check if the loopmount succeeds with commands mount and losetup -a. As I see it the debug verbosity should be raised because we can now not see what exactly goes wrong.
- -- Kind regards,
Jeroen van Meeuwen - -kanarip
- -- http://www.kanarip.com/ RHCE, LPIC-2, MCP, CCNA C6B0 7FB4 43E6 CDDA D258 F70B 28DE 9FDA 9342 BF08
On søn, aug 26, 2007 at 04:57:18 +0200, Jeroen van Meeuwen wrote:
Lars Bjørndal wrote:
On søn, aug 26, 2007 at 12:54:05 +0200, Jeroen van Meeuwen wrote:
I didn't get this error running from either GIT or revisor-2.0.4.3-1rc1 (soon to land in the development repo). Can you reproduce from the latest GIT version?
Yes, I can. I did a new GIT install today, and I got the same error message. Do you need my config files etc.?
I use some files from my own repo, could that be a problem? What does the error message actually indicate?
Lars
Setting up the installation target is merely providing a loopmounted ext3 filesystem. You could check if the loopmount succeeds with commands mount and losetup -a. As I see it the debug verbosity should be raised because we can now not see what exactly goes wrong.
Output from mount, after aborting, is:
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw) /dev/proc on /proc type proc (rw) /dev/sys on /sys type sysfs (rw) /dev/devpts on /dev/pts type devpts (rw,gid=5,mode=620) /dev/sda1 on /boot type ext3 (rw) /dev/shm on /dev/shm type tmpfs (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) /dev/loop0 on / type ext3 (rw)
- losetup -a /dev/loop0: [fd00]:97928 (/var/tmp/revisor-livecd/data/os.img)
Lars
Lars Bjørndal lars.bjorndal@broadpark.no writes:
On søn, aug 26, 2007 at 04:57:18 +0200, Jeroen van Meeuwen wrote:
Lars Bjørndal wrote:
On søn, aug 26, 2007 at 12:54:05 +0200, Jeroen van Meeuwen wrote:
I didn't get this error running from either GIT or revisor-2.0.4.3-1rc1 (soon to land in the development repo). Can you reproduce from the latest GIT version?
Yes, I can. I did a new GIT install today, and I got the same error message. Do you need my config files etc.?
I use some files from my own repo, could that be a problem? What does the error message actually indicate?
Lars
Setting up the installation target is merely providing a loopmounted ext3 filesystem. You could check if the loopmount succeeds with commands mount and losetup -a. As I see it the debug verbosity should be raised because we can now not see what exactly goes wrong.
Output from mount, after aborting, is:
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw) /dev/proc on /proc type proc (rw) /dev/sys on /sys type sysfs (rw) /dev/devpts on /dev/pts type devpts (rw,gid=5,mode=620) /dev/sda1 on /boot type ext3 (rw) /dev/shm on /dev/shm type tmpfs (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) /dev/loop0 on / type ext3 (rw)
- losetup -a
/dev/loop0: [fd00]:97928 (/var/tmp/revisor-livecd/data/os.img)
Hello!
What could I do to go on solving this problem, do you think?
Lars
Hello!
I still cannot manage to create a --live-optical CD with revisor. Yesterday, I downloaded and installed both revisor and livecd-tools from GIT.
I ran the command:
revisor --model=lrs --live-optical --debug
The model lrs is a modified f7, with yum.conf set as config file.
Some of the output was:
{'modrebrand': False, 'modjigdo': False, 'modcobbler': False, 'moddelta': False, 'modvirt': False} Setting default options Setting options from configuration file Reading configuration file /etc/revisor/revisor.conf Setting repos_enabledevelopment to 0 (from configuration file) Setting repos_enabletesting to 0 (from configuration file) Setting media_installation_cd to 0 (from configuration file) Setting media_installation_dvd to 0 (from configuration file) Setting mode_respin to 0 (from configuration file) Setting repos_enablesource to 0 (from configuration file) Setting media_live_optical to 0 (from configuration file) Setting dependency_resolve_allow_conflicts to 0 (from configuration file) Setting repos_enabledebuginfo to 0 (from configuration file) Setting media_live_thumb to 0 (from configuration file) Using model lrs, as specified by --model Setting architecture to 'i386' (from configuration file model lrs) Setting iso_basename to 'F' (from configuration file model lrs) Setting getsource to 0 (from configuration file model lrs) Setting version to '7' (from configuration file model lrs) Setting product_path to 'Fedora' (from configuration file model lrs) Setting product_name to 'Fedora' (from configuration file model lrs) Setting comps to '/usr/share/revisor/comps/comps-f7.xml' (from configuration file model lrs) Setting options from command-line Running Revisor in CLI mode... Running main routine... Running in CLI mode... Setting architecture to 'i386' (from configuration file model lrs) Setting iso_basename to 'F' (from configuration file model lrs) Setting getsource to 0 (from configuration file model lrs) Setting version to '7' (from configuration file model lrs) Setting product_path to 'Fedora' (from configuration file model lrs) Setting product_name to 'Fedora' (from configuration file model lrs) Setting comps to '/usr/share/revisor/comps/comps-f7.xml' (from configuration file model lrs) Checking working directories The directories Revisor uses in /var/tmp/ already exist. This could possibly hold data from a previous run. Please remove or move them to a safe location, then confirm to continue. If you do not move or remove the files, Revisor will simply delete them. Do you want to continue? [Y/n] y
...
Downloading Packages: Initting progress bar for Setting up Ext3 Filesystem Setting up Ext3 Filesystem: Setting up Ext3 Filesystem: 0.0% mke2fs 1.40.2 (12-Jul-2007) Filesystem label=livecd-20070830 OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 219072 inodes, 437504 blocks 4375 blocks (1.00%) reserved for the super user First data block=0 Maximum filesystem blocks=448790528 14 block groups 32768 blocks per group, 32768 fragments per group 15648 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912
Writing inode tables: 0/14 Creating journal (8192 blocks): done Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 32 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. tune2fs 1.40.2 (12-Jul-2007) Setting maximal mount count to -1 Setting interval between checks to 0 seconds Cannot setup installation target. Aborting. Do you want to continue? [Y/n] y
[root@cd ~]# mount /dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw) /dev/proc on /proc type proc (rw) /dev/sys on /sys type sysfs (rw) /dev/devpts on /dev/pts type devpts (rw,gid=5,mode=620) /dev/sda1 on /boot type ext3 (rw) /dev/shm on /dev/shm type tmpfs (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) /dev/loop0 on / type ext3 (rw)
[root@cd ~]# losetup -a /dev/loop0: [fd00]:130579 (/var/tmp/revisor-livecd/data/os.img)
[root@cd ~]# ls -al /var/tmp/revisor-livecd/data/os.img -rwxr-xr-x 1 root root 1792016385 2007-08-30 15:33 /var/tmp/revisor-livecd/data/os.img
What can I do, I wonder?
Lars
Lars Bjørndal wrote:
Hello!
I still cannot manage to create a --live-optical CD with revisor. Yesterday, I downloaded and installed both revisor and livecd-tools from GIT.
I have next to no experience with revisor, but this is the second time I've seen something like this on this list-
[root@cd ~]# mount /dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
...
/dev/loop0 on / type ext3 (rw)
[root@cd ~]# losetup -a /dev/loop0: [fd00]:130579 (/var/tmp/revisor-livecd/data/os.img)
What is up with that? ('/dev/loop0' mounted(???) on '/')
That would make me a bit anxious if I saw it on my system... Or is it just some weird chroot/mtab/fstab artifact causing the output of mount to not actually reflect reality?
Mainly this goes to my fear of running something like livecd-creator as root... (even if the only other way involves virtualization and 10X slowdown in performance)
-dmc
Douglas McClendon wrote:
Lars Bjørndal wrote:
Hello!
I still cannot manage to create a --live-optical CD with revisor. Yesterday, I downloaded and installed both revisor and livecd-tools from GIT.
I have next to no experience with revisor, but this is the second time I've seen something like this on this list-
One has got to know that GIT is unstable; It eats babies. For breakfast. If you happen to clone anything I'm just pushing from my -devel to my -test machine, and it destroys your machine, you're busted.
Use the tags; we use them to mark a point at which we think there's no regression in what was in the feature set of a previous /release/.
Bugs get fixed, GIT is updated multiple times a day; check what is in the commit logs before you make your move; we often message "Oops" and "Let's try this or that".
[root@cd ~]# mount /dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
...
/dev/loop0 on / type ext3 (rw)
[root@cd ~]# losetup -a /dev/loop0: [fd00]:130579 (/var/tmp/revisor-livecd/data/os.img)
What commit does this exactly?
Kind regards,
Jeroen van Meeuwen -kanarip
Jeroen van Meeuwen kanarip@kanarip.com writes:
Douglas McClendon wrote:
Lars Bjørndal wrote:
[root@cd ~]# mount /dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
...
/dev/loop0 on / type ext3 (rw)
[root@cd ~]# losetup -a /dev/loop0: [fd00]:130579 (/var/tmp/revisor-livecd/data/os.img)
What commit does this exactly?
0ad6a3da49ff75fbfcd5802c5b03de51d9d014ac
Maybe the problem is related to that I'm using the /etc/yum.conf file. The cache dir is then set to /var/cache/yum, and not to a directory under /var/tmp/revisor. Maybe the files are not found then?
I'll have a look in that direction.
Lars
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Lars Bjørndal wrote:
Jeroen van Meeuwen kanarip@kanarip.com writes:
Douglas McClendon wrote:
Lars Bjørndal wrote:
[root@cd ~]# mount /dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
...
/dev/loop0 on / type ext3 (rw)
[root@cd ~]# losetup -a /dev/loop0: [fd00]:130579 (/var/tmp/revisor-livecd/data/os.img)
What commit does this exactly?
0ad6a3da49ff75fbfcd5802c5b03de51d9d014ac
Maybe the problem is related to that I'm using the /etc/yum.conf file.
Please, do not use the /etc/yum.conf. Any variables used in /etc/yum.conf and the repository configuration do not get expanded. The installroot of /etc/yum.conf is "/". That also explains how os.img gets mounted there.
Use the revisor yum configuration files in /etc/revisor/conf.d/, create your own or modify these.
- -- Kind regards,
Jeroen van Meeuwen - -kanarip
- -- http://www.kanarip.com/ RHCE, LPIC-2, MCP, CCNA C6B0 7FB4 43E6 CDDA D258 F70B 28DE 9FDA 9342 BF08
livecd@lists.fedoraproject.org
-
Douglas McClendon -
Jeroen van Meeuwen -
Lars Bjørndal