Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[SOLVED] emerge --sync issues. no space left on device.
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
imcominup
Apprentice
Apprentice


Joined: 07 Jan 2007
Posts: 176

PostPosted: Mon Aug 27, 2007 3:31 am    Post subject: [SOLVED] emerge --sync issues. no space left on device. Reply with quote

this is the message given at the end of emerge --sync
Code:

receiving file list ... done
rsync: recv_generator: mkdir "/usr/portage/dev-games/ois" failed: No space left on device (28)
*** Skipping everything below this failed directory ***
rsync: recv_generator: mkdir "/usr/portage/dev-java/commons-configuration" failed: No space left on device (28)
*** Skipping everything below this failed directory ***
rsync: mkstemp "/usr/portage/app-admin/eselect-blas/.ChangeLog.q9leM8" failed: No space left on device (28)
rsync: mkstemp "/usr/portage/app-admin/eselect-blas/.Manifest.H9btCb" failed: No space left on device (28)
rsync: mkstemp "/usr/portage/app-admin/eselect-blas/.eselect-blas-0.1.ebuild.l1Bdte" failed: No space left on device (28)
rsync: mkstemp "/usr/portage/app-admin/eselect-emacs/.ChangeLog.GIEYjh" failed: No space left on device (28)
rsync: mkstemp "/usr/portage/app-admin/eselect-emacs/.Manifest.9Bfvbk" failed: No space left on device (28)
rsync: mkstemp "/usr/portage/app-admin/eselect-emacs/.eselect-emacs-1.1.ebuild.wxgu3m" failed: No space left on device (28)
rsync: mkstemp "/usr/portage/app-admin/eselect-fontconfig/.Manifest.aW0tVp" failed: No space left on device (28)
rsync: mkstemp "/usr/portage/app-admin/eselect-fontconfig/.eselect-fontconfig-1.0.ebuild.jnGhYs" failed: No space left on device (28)
app-admin/eselect/
app-admin/eselect/Manifest
rsync: write failed on "/usr/portage/app-admin/eselect/Manifest": No space left on device (28)
rsync error: error in file IO (code 11) at receiver.c(258) [receiver=2.6.9]
rsync: connection unexpectedly closed (3446450 bytes received so far) [generator]
rsync error: error in rsync protocol data stream (code 12) at io.c(453) [generator=2.6.9]

!!! Rsync has not successfully finished. It is recommended that you keep
!!! trying or that you use the 'emerge-webrsync' option if you are unable
!!! to use rsync due to firewall or other restrictions. This should be a
!!! temporary problem unless complications exist with your network
!!! (and possibly your system's filesystem) configuration.


there are no firewalls, no problems with my connection. i'm using reiserfs as a filesystem, and i'm pretty sure i've synced before with no problems. any suggestions? the error says there is no space left on my device.

Code:

kumi@throne ~ $ df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/hda3               497964    127188    370776  26% /
udev                    453060       116    452944   1% /dev
/dev/hda1                96312     38788     57524  41% /boot
/dev/hda5               979868    137248    842620  15% /tmp
/dev/hda6              4883556    394956   4488600   9% /opt
/dev/hda7              1951744    450472   1501272  24% /var
/dev/hda8              7815308   4377056   3438252  57% /usr
/dev/hda9            226011528  27488252 198523276  13% /home
shm                     453060         0    453060   0% /dev/shm
/usr/portage_volume     614376    614376         0 100% /usr/portage


how do i clean it out? just sudo rm -rf /usr/portage? is that safe?

here's my make.conf
Code:

CHOST="i686-pc-linux-gnu"
CFLAGS="-O2 -mtune=athlon-xp -march=athlon-xp -finline-functions -falign-jumps=16 -falign-loops=16 -falign-functions=64 -fprefetch-loop-arrays -fomit-frame-pointer -fforce-addr -pipe"
CXXFLAGS="-O2 -pipe"
USE="alsa mp3 dts dvd dvdread udev xv jpeg jpg png cdr firefox bzip2 java mmx mmxext sse sse2 ssl doc 3dnow 3dnowext -eds unicode doc gnutls ldap nls nptl nptlonly -real readline ipv6 kerberos X xorg -kde gtk -qt -arts -cups alsa oss -dlloader apache2 php"
ACCEPT_KEYWORDS="x86"
PORTAGE_TMPDIR=/var/tmp
PORTDIR=/usr/portage
DISTDIR=/mnt/distfiles
PKGDIR=/mnt/packages
PORT_LOGDIR=/var/log/portage
PORTDIR_OVERLAY=/usr/local/portage
GENTOO_MIRRORS="http://gentoo.osuosl.org http://www.ibiblio.org/pub/Linux/distributions/gentoo"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
#PORTAGE_RSYNC_EXTRA_OPTS="--exclude-from=/etc/portage/rsync_excludes"
RSYNC_RETRIES="3"
RSYNC_TIMEOUT=180
MAKEOPTS="-j3"
PORTAGE_NICENESS=15
AUTOCLEAN="yes"
FEATURES="ccache distlocks distclean sandbox throne userpriv usersandbox candy"
CCACHE_SIZE="80M"
#FETCHCOMMAND="/usr/bin/axel -a -o /\${DISTDIR}/\${FILE} \${URI}"
#RESUMECOMMAND="/usr/bin/axel -a -o /\${DISTDIR}/\${FILE} \${URI}"
LINGUAS="en"
LDFLAGS="-Wl,-O1 -Wl,--sort-common"
#LDFLAGS="-W1,-O1 -W1,--enable-new-dtags -W1,--sort-common -s -W1,--as-needed -WL,-zdynsort"
VIDEO_CARDS="radeon ati vesa"


anything else i'm missing here?


Last edited by imcominup on Mon Aug 27, 2007 5:34 pm; edited 1 time in total
Back to top
View user's profile Send private message
didymos
Advocate
Advocate


Joined: 10 Oct 2005
Posts: 4798
Location: California

PostPosted: Mon Aug 27, 2007 3:45 am    Post subject: Reply with quote

Quite simply, the partition is too small. Not by much, but enough. Using du, which is not exact, but close enough, a just synced tree is 745M on ext3. You can exclude parts of the tree, but it would have been better to have used a larger partition in the first place. What exactly are you using anyway? Is this a file mounted using the loopback device?
_________________
Thomas S. Howard
Back to top
View user's profile Send private message
i92guboj
Bodhisattva
Bodhisattva


Joined: 30 Nov 2004
Posts: 10315
Location: Córdoba (Spain)

PostPosted: Mon Aug 27, 2007 3:56 am    Post subject: Reply with quote

didymos wrote:
Quite simply, the partition is too small. Not by much, but enough. Using du, which is not exact, but close enough, a just synced tree is 745M on ext3. You can exclude parts of the tree, but it would have been better to have used a larger partition in the first place. What exactly are you using anyway? Is this a file mounted using the loopback device?


That space is more than enough to hold portage, but he probably needs to reformat it with -i 1024. The problem is surely he's getting out of i-nodes (it can be checked with df -i). With such i-node size, my portage fits into 364 mb). Since portage continuously grows, it is possible that you had enough i-nodes to hold it a few weeks ago, but probably you don't have enough i-nodes to hold it right now. I am not sure about reiserfs, but on ext3 you should be able to format with an even smaller i-node size, down to 512 bytes.

Smaller i-nodes means more i-nodes in a disk, which means that the maximum number of files will also grow.
Back to top
View user's profile Send private message
imcominup
Apprentice
Apprentice


Joined: 07 Jan 2007
Posts: 176

PostPosted: Mon Aug 27, 2007 4:02 am    Post subject: Reply with quote

didymos wrote:
Quite simply, the partition is too small. Not by much, but enough. Using du, which is not exact, but close enough, a just synced tree is 745M on ext3. You can exclude parts of the tree, but it would have been better to have used a larger partition in the first place. What exactly are you using anyway? Is this a file mounted using the loopback device?


to answer your question. i have no idea. my friend setup this gentoo box for me while i was learning linux. i still am learning, i chose a relatively difficult distro to force me to learn everything. what do you need to know about my system (and how can i get that information for you) to help me.
Back to top
View user's profile Send private message
i92guboj
Bodhisattva
Bodhisattva


Joined: 30 Nov 2004
Posts: 10315
Location: Córdoba (Spain)

PostPosted: Mon Aug 27, 2007 4:11 am    Post subject: Reply with quote

imcominup wrote:
didymos wrote:
Quite simply, the partition is too small. Not by much, but enough. Using du, which is not exact, but close enough, a just synced tree is 745M on ext3. You can exclude parts of the tree, but it would have been better to have used a larger partition in the first place. What exactly are you using anyway? Is this a file mounted using the loopback device?


to answeryour question. i have no idea. my friend setup this gentoo box for me while i was learning linux. i still am learning, i chose a relatively difficult distro to force me to learn everything. what do you need to know about my system (and how can i get that information for you) to help me.


That partition is nothing vital to run. You can just do this, as root:

Code:

$ cd ~
$ umount /usr/portage
$ mkfs.<whatever fs you choose> -i 1024 /dev/portage_volume


Then mount it again, and emerge --sync to fill the partition with a new copy of the portage tree. It will take some time because you will need to download the whole portage tree again. Just choose the right mkfs.* command for your filesystem.
Back to top
View user's profile Send private message
didymos
Advocate
Advocate


Joined: 10 Oct 2005
Posts: 4798
Location: California

PostPosted: Mon Aug 27, 2007 4:14 am    Post subject: Reply with quote

i92guboj wrote:
That space is more than enough to hold portage, but he probably needs to reformat it with -i 1024. The problem is surely he's getting out of i-nodes (it can be checked with df -i). With such i-node size, my portage fits into 364 mb).


Yeah, actually, you're probably right. I'm using a 4096 block size, so that inflates things quite a bit. By adding "--apparent-size" to du, the total comes out to only 450M.
_________________
Thomas S. Howard
Back to top
View user's profile Send private message
imcominup
Apprentice
Apprentice


Joined: 07 Jan 2007
Posts: 176

PostPosted: Mon Aug 27, 2007 4:45 am    Post subject: Reply with quote

im using reiserfs. so would it be...
Code:

kumi@throne ~ # umount /usr/portage
kumi@throne ~ # mkfs.reiserfs -i 1024 /dev/portage_volume


then what?
Back to top
View user's profile Send private message
didymos
Advocate
Advocate


Joined: 10 Oct 2005
Posts: 4798
Location: California

PostPosted: Mon Aug 27, 2007 5:05 am    Post subject: Reply with quote

Remount and run "emerge --sync".
_________________
Thomas S. Howard
Back to top
View user's profile Send private message
Akkara
Bodhisattva
Bodhisattva


Joined: 28 Mar 2006
Posts: 6702
Location: &akkara

PostPosted: Mon Aug 27, 2007 5:18 am    Post subject: Reply with quote

If you haven't yet remade the partition and want to save some time and bandwidth re-downloading, you can copy /usr/portage somewhere else then copy it back. If you do, be sure to preserve the file dates because that is what sync uses to know what needs updating. For example:
Code:
mkdir /var/tmp/hold
cp -ar /usr/portage /var/tmp/hold
umount /usr/portage

# (make your filesystem however you'd like)
mkfs.reiserfs -i 1024 /usr/portage_volume

mount /usr/portage
cp -ar /var/tmp/hold/portage/. /usr/portage
emerge --sync # pick up any still-missing changes


You can even try unmounting and re-making the filesystem in different ways, copying back each time, until you find something that works best.

Once you're happy with the new filesystem,
Code:
rm -r /var/tmp/hold


Last edited by Akkara on Mon Aug 27, 2007 5:30 am; edited 2 times in total
Back to top
View user's profile Send private message
imcominup
Apprentice
Apprentice


Joined: 07 Jan 2007
Posts: 176

PostPosted: Mon Aug 27, 2007 5:19 am    Post subject: Reply with quote

didymos wrote:
Remount and run "emerge --sync".


where in those commands greatens the portage partition? what is going on here exactly?
Back to top
View user's profile Send private message
Akkara
Bodhisattva
Bodhisattva


Joined: 28 Mar 2006
Posts: 6702
Location: &akkara

PostPosted: Mon Aug 27, 2007 5:30 am    Post subject: Reply with quote

imcominup wrote:
Code:

kumi@throne ~ # umount /usr/portage
kumi@throne ~ # mkfs.reiserfs -i 1024 /dev/portage_volume

then what?
didymos wrote:
Remount and run "emerge --sync".


Where in those commands greatens the portage partition? what is going on here exactly?


Do you mean "creates" when you wrote "greatens"?

From looking at your "df" list, it seems you are using a file (/usr/portage_volume) that holds a filesystem which is mounted with the loopback option which becomes visible as /usr/portage. So there's no specific partition in the usual sense, a file takes its place.

That file (/usr/portage_volume) is still there, so does not need to be re-created. What the mkfs line did was to re-create the filesystem image on that file.

Does this answer your question?
Back to top
View user's profile Send private message
imcominup
Apprentice
Apprentice


Joined: 07 Jan 2007
Posts: 176

PostPosted: Mon Aug 27, 2007 5:52 am    Post subject: Reply with quote

what i meant by greatens i meant 'making bigger'. because that is what seems to be the error during syncing. so where do those commands illustrate that? do they at all?
Back to top
View user's profile Send private message
desultory
Bodhisattva
Bodhisattva


Joined: 04 Nov 2005
Posts: 9410

PostPosted: Mon Aug 27, 2007 6:32 am    Post subject: Reply with quote

The purpose of these changes is not to expand the total space available for files in /usr/portage, it is to increase the number of files which can be placed there by modifying how the available space is allocated.
Back to top
View user's profile Send private message
imcominup
Apprentice
Apprentice


Joined: 07 Jan 2007
Posts: 176

PostPosted: Mon Aug 27, 2007 6:36 am    Post subject: Reply with quote

desultory wrote:
The purpose of these changes is not to expand the total space available for files in /usr/portage, it is to increase the number of files which can be placed there by modifying how the available space is allocated.


thank you so much for that inciteful post. that makes much more sense. i am following akkara's post and creating a temporary copy of my portage tree and then remounting it with a 1024 filesystem, and copying it back. i'll let you know how it goes. gimme a few.
Back to top
View user's profile Send private message
imcominup
Apprentice
Apprentice


Joined: 07 Jan 2007
Posts: 176

PostPosted: Mon Aug 27, 2007 6:40 am    Post subject: Reply with quote

having some trouble with mkfs.reiserfs
Code:

kumi@throne /var/tmp $ sudo cp -ar /usr/portage /var/tmp/hold/
kumi@throne /var/tmp $ sudo umount /usr/portage
Password:
kumi@throne /var/tmp $ cd
kumi@throne ~ $ sudo mkfs.reiserfs -i 1024 /usr/portage_volume
mkfs.reiserfs: invalid option -- i
Usage: mkfs.reiserfs [options]  device [block-count]

Options:

  -b | --block-size N              size of file-system block, in bytes
  -j | --journal-device FILE       path to separate device to hold journal
  -s | --journal-size N            size of the journal in blocks
  -o | --journal-offset N          offset of the journal from the start of
                                   the separate device, in blocks
  -t | --transaction-max-size N    maximal size of transaction, in blocks
  -B | --badblocks file            store all bad blocks given in file on the fs
  -h | --hash rupasov|tea|r5       hash function to use by default
  -u | --uuid UUID                 store UUID in the superblock
  -l | --label LABEL               store LABEL in the superblock
  --format 3.5|3.6                 old 3.5 format or newer 3.6
  -f | --force                     specified once, make mkreiserfs the whole
                                   disk, not block device or mounted partition;
                                   specified twice, do not ask for confirmation
  -q | --quiet                     quiet work without messages, progress and
                                   questions. Useful if run in a script. For use
                                   by end users only.
  -d | --debug                     print debugging information during mkreiser
  -V                               print version and exit

it seems the -i option doesn't work. maybe it should have been -b or -s? any ideas?
Back to top
View user's profile Send private message
neysx
Retired Dev
Retired Dev


Joined: 27 Jan 2003
Posts: 795

PostPosted: Mon Aug 27, 2007 7:00 am    Post subject: Reply with quote

Don't user reiserfs for your portage tree. (or for anything else, but that's just my opinion ;-) )
ext2 is all you need for your tree: mke2fs -m 0 -b 1024 -N 220000 /usr/portage_volume
-m 0: 0% reserved for root
-b 1024: 1K blocks, plenty of small files, thus less slack is wasted
-N 220000: plenty of inodes, i.e. you need plenty of files in there, that's what you ran short of

hth
Back to top
View user's profile Send private message
imcominup
Apprentice
Apprentice


Joined: 07 Jan 2007
Posts: 176

PostPosted: Mon Aug 27, 2007 7:21 am    Post subject: Reply with quote

what's wrong with reiserfs? my entire filesystem was built with reiserfs. anyway i'm competely up for info when it comes to anything gentoo.

Code:
kumi@throne ~ $ sudo mke2fs -m 0 -b 1024 -N 220000 /usr/portage_volume
Password:
mke2fs 1.39 (29-May-2006)
/usr/portage_volume is not a block special device.
Proceed anyway? (y,n) n
kumi@throne ~ $ sudo mkfs.reiserfs -b 1024 /usr/portage_volume
mkfs.reiserfs 3.6.19 (2003 www.namesys.com)

A pair of credits:
BigStorage  (www.bigstorage.com)  contributes to our general fund  every mont
and has done so for quite a long time.

Edward Shushkin wrote the encryption and compression  file plugins,  and the
journal relocation code.


/usr/portage_volume is not a block special device
Use -f to force over


what's the deal here? what does 'not a block special device' mean?
Back to top
View user's profile Send private message
desultory
Bodhisattva
Bodhisattva


Joined: 04 Nov 2005
Posts: 9410

PostPosted: Mon Aug 27, 2007 7:31 am    Post subject: Reply with quote

Block special devices are how things like hard drives and memory cards, things which store data in blocks of a given size, are access. The file /usr/portage_volume is a regular file, it is not special in that regard. With the file in place and of the appropriate size add -F to the options you gave to mke2fs and it will, barring mishaps, create a file system there even though it is a regular file.
Back to top
View user's profile Send private message
imcominup
Apprentice
Apprentice


Joined: 07 Jan 2007
Posts: 176

PostPosted: Mon Aug 27, 2007 7:42 am    Post subject: Reply with quote

desultory wrote:
Block special devices are how things like hard drives and memory cards, things which store data in blocks of a given size, are access. The file /usr/portage_volume is a regular file, it is not special in that regard. With the file in place and of the appropriate size add -F to the options you gave to mke2fs and it will, barring mishaps, create a file system there even though it is a regular file.


thanks for that, bud.

Code:

kumi@throne ~ $ sudo mke2fs -m 0 -b 1024 -N 220000 -F /usr/portage_volume
Password:
mke2fs 1.39 (29-May-2006)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
220200 inodes, 614400 blocks
0 blocks (0.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67895296
75 block groups
8192 blocks per group, 8192 fragments per group
2936 inodes per group
Superblock backups stored on blocks:
        8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409

Writing inode tables: done                           
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 37 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
kumi@throne ~ $ sudo mount /usr/portage
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

kumi@throne ~ $ dmesg
PI: PM-Timer IO Port: 0x1008
Allocating PCI resources starting at 50000000 (gap: 40000000:90000000)
Detected 2412.424 MHz processor.
Built 1 zonelists.  Total pages: 229376
Kernel command line: root=/dev/hda3
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 16384 bytes)
spurious 8259A interrupt: IRQ7.
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 905900k/917504k available (2065k kernel code, 11128k reserved, 762k data, 132k i                          nit, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 4826.90 BogoMIPS (lpj=24134502)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 078bfbff e3d3fbff 00000000 00000000 00000001 00000000                           00000001
CPU: After vendor identify, caps: 078bfbff e3d3fbff 00000000 00000000 00000001 00000000                           00000001
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
CPU: After all inits, caps: 078bfbff e3d3fbff 00000000 00000410 00000001 00000000 000000                          01
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to ffffe000.
CPU: AMD Athlon(tm) 64 Processor 4000+ stepping 01
Checking 'hlt' instruction... OK.
ACPI: Core revision 20060707
ACPI: setting ELCR to 0200 (from 0cb8)
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: Using MMCONFIG
PCI: No mmconfig possible on 0:18
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
PCI: Transparent bridge - 0000:00:09.0
Boot video device is 0000:05:00.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNK2] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNK3] (IRQs 3 4 5 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK4] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNK5] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LUBA] (IRQs *3 4 5 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LUBB] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LMAC] (IRQs 3 4 5 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LACI] (IRQs 3 4 *5 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LMCI] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LSMB] (IRQs 3 *4 5 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LUB2] (IRQs 3 4 5 *7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LIDE] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LSID] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LFID] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LPCA] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [APC1] (IRQs 16) *0, disabled.
ACPI: PCI Interrupt Link [APC2] (IRQs 17) *0, disabled.
ACPI: PCI Interrupt Link [APC3] (IRQs 18) *0, disabled.
ACPI: PCI Interrupt Link [APC4] (IRQs 19) *0, disabled.
ACPI: PCI Interrupt Link [APC5] (IRQs *16), disabled.
ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APCS] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APSI] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APSJ] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APCP] (IRQs 20 21 22 23) *0, disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 12 devices
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
pnp: 00:01: ioport range 0x1000-0x107f could not be reserved
pnp: 00:01: ioport range 0x1080-0x10ff has been reserved
pnp: 00:01: ioport range 0x1400-0x147f has been reserved
pnp: 00:01: ioport range 0x1480-0x14ff could not be reserved
pnp: 00:01: ioport range 0x1800-0x187f has been reserved
pnp: 00:01: ioport range 0x1880-0x18ff has been reserved
PCI: Bridge: 0000:00:09.0
  IO window: disabled.
  MEM window: f2000000-f20fffff
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:0b.0
  IO window: b000-bfff
  MEM window: disabled.
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:0c.0
  IO window: a000-afff
  MEM window: disabled.
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:0d.0
  IO window: 9000-9fff
  MEM window: disabled.
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:0e.0
  IO window: c000-cfff
  MEM window: f0000000-f1ffffff
  PREFETCH window: e0000000-efffffff
PCI: Setting latency timer of device 0000:00:09.0 to 64
PCI: Setting latency timer of device 0000:00:0b.0 to 64
PCI: Setting latency timer of device 0000:00:0c.0 to 64
PCI: Setting latency timer of device 0000:00:0d.0 to 64
PCI: Setting latency timer of device 0000:00:0e.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
Machine check exception polling timer started.
fuse init (API version 7.7)
io scheduler noop registered
io scheduler cfq registered (default)
PCI: Linking AER extended capability on 0000:00:0b.0
PCI: Linking AER extended capability on 0000:00:0c.0
PCI: Linking AER extended capability on 0000:00:0d.0
PCI: Linking AER extended capability on 0000:00:0e.0
PCI: Setting latency timer of device 0000:00:0b.0 to 64
pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:0b.0:pcie00]
Allocate Port Service[0000:00:0b.0:pcie03]
PCI: Setting latency timer of device 0000:00:0c.0 to 64
pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:0c.0:pcie00]
Allocate Port Service[0000:00:0c.0:pcie03]
PCI: Setting latency timer of device 0000:00:0d.0 to 64
pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:0d.0:pcie00]
Allocate Port Service[0000:00:0d.0:pcie03]
PCI: Setting latency timer of device 0000:00:0e.0 to 64
pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:0e.0:pcie00]
Allocate Port Service[0000:00:0e.0:pcie03]
Real Time Clock Driver v1.12ac
Non-volatile memory driver v1.2
ACPI: Getting cpuindex for acpiid 0x1
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
loop: loaded (max 8 devices)
e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.56.
ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LMAC] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:00:0a.0 to 64
forcedeth: using HIGHDMA
input: AT Translated Set 2 keyboard as /class/input/input0
eth0: forcedeth.c: subsystem: 01458:e000 bound to 0000:00:0a.0
Linux video capture interface: v2.00
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE-CK804: IDE controller at PCI slot 0000:00:06.0
NFORCE-CK804: chipset revision 242
NFORCE-CK804: not 100% native mode: will probe irqs later
NFORCE-CK804: 0000:00:06.0 (rev f2) UDMA133 controller
    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide0...
input: ImExPS/2 Generic Explorer Mouse as /class/input/input1
hda: WDC WD2500JB-00REA0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: _NEC DVD_RW ND-3550A, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 512KiB
hda: Host Protected Area detected.
        current capacity is 488395055 sectors (250058 MB)
        native  capacity is 488397168 sectors (250059 MB)
hda: Host Protected Area disabled.
hda: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63, UDMA(100)
hda: cache flushes supported
 hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 hda9 >
hdc: ATAPI 48X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
usbmon: debugfs is not available
ACPI: PCI Interrupt Link [LUB2] enabled at IRQ 7
PCI: setting IRQ 7 as level-triggered
ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [LUB2] -> GSI 7 (level, low) -> IRQ 7
PCI: Setting latency timer of device 0000:00:02.1 to 64
ehci_hcd 0000:00:02.1: EHCI Host Controller
ehci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:02.1: debug port 1
PCI: cache line size of 64 is not supported by device 0000:00:02.1
ehci_hcd 0000:00:02.1: irq 7, io mem 0xfeb00000
ehci_hcd 0000:00:02.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 10 ports detected
USB Universal Host Controller Interface driver v3.0
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
i2c /dev entries driver
i2c_adapter i2c-0: nForce2 SMBus adapter at 0x1c00
i2c_adapter i2c-1: nForce2 SMBus adapter at 0x1c40
Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22 13:55:50 2006 UTC                          ).
ALSA device list:
  No soundcards found.
ip_conntrack version 2.4 (7168 buckets, 57344 max) - 172 bytes per conntrack
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
ReiserFS: hda3: found reiserfs format "3.6" with standard journal
Time: tsc clocksource has been installed.
ReiserFS: hda3: using ordered data mode
ReiserFS: hda3: journal params: device hda3, size 8192, journal first block 18, max tran                          s len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda3: checking transaction log (hda3)
ReiserFS: hda3: Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Freeing unused kernel memory: 132k freed
ACPI: PCI Interrupt Link [LACI] enabled at IRQ 5
PCI: setting IRQ 5 as level-triggered
ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [LACI] -> GSI 5 (level, low) -> IRQ 5
PCI: Setting latency timer of device 0000:00:04.0 to 64
intel8x0_measure_ac97_clock: measured 56867 usecs
intel8x0: clocking to 46927
ACPI: PCI Interrupt Link [LNK3] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt 0000:01:06.0[A] -> Link [LNK3] -> GSI 10 (level, low) -> IRQ 10
rt2500 1.1.0 BETA4 2006/06/18 http://rt2x00.serialmonkey.com
ReiserFS: hda1: found reiserfs format "3.6" with standard journal
ReiserFS: hda1: using ordered data mode
ReiserFS: hda1: journal params: device hda1, size 8192, journal first block 18, max tran                          s len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda1: checking transaction log (hda1)
ReiserFS: hda1: Using r5 hash to sort names
ReiserFS: hda5: found reiserfs format "3.6" with standard journal
ReiserFS: hda5: using ordered data mode
ReiserFS: hda5: journal params: device hda5, size 8192, journal first block 18, max tran                          s len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda5: checking transaction log (hda5)
ReiserFS: hda5: Using r5 hash to sort names
ReiserFS: hda6: found reiserfs format "3.6" with standard journal
ReiserFS: hda6: using ordered data mode
ReiserFS: hda6: journal params: device hda6, size 8192, journal first block 18, max tran                          s len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda6: checking transaction log (hda6)
ReiserFS: hda6: Using r5 hash to sort names
ReiserFS: hda7: found reiserfs format "3.6" with standard journal
ReiserFS: hda7: using ordered data mode
ReiserFS: hda7: journal params: device hda7, size 8192, journal first block 18, max tran                          s len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda7: checking transaction log (hda7)
ReiserFS: hda7: Using r5 hash to sort names
ReiserFS: hda8: found reiserfs format "3.6" with standard journal
ReiserFS: hda8: using ordered data mode
ReiserFS: hda8: journal params: device hda8, size 8192, journal first block 18, max tran                          s len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda8: checking transaction log (hda8)
ReiserFS: hda8: Using r5 hash to sort names
ReiserFS: hda9: found reiserfs format "3.6" with standard journal
ReiserFS: hda9: using ordered data mode
ReiserFS: hda9: journal params: device hda9, size 8192, journal first block 18, max tran                          s len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda9: checking transaction log (hda9)
ReiserFS: hda9: Using r5 hash to sort names
ReiserFS: loop0: found reiserfs format "3.6" with standard journal
ReiserFS: loop0: using ordered data mode
ReiserFS: loop0: journal params: device loop0, size 8192, journal first block 18, max tr                          ans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: loop0: checking transaction log (loop0)
ReiserFS: loop0: Using r5 hash to sort names
Unable to find swap-space signature
eth0: no link during initialization.
rt2500 EEPROM:  1  2  3  4  5  6  7  8  9 10 11 12 13 14  Channel
rt2500 EEPROM:  6  6  6  6  7  7  7  7  7  7  7  7  7  7  dBm Maximum
Linux agpgart interface v0.101 (c) Dave Jones
fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' tai                          nts kernel.
[fglrx] Maximum main memory to use for locked dma buffers: 804 MBytes.
[fglrx] module loaded - fglrx 8.30.3 [Oct 26 2006] on minor 0
ACPI: PCI Interrupt 0000:05:00.0[A] -> Link [LNK3] -> GSI 10 (level, low) -> IRQ 10
[fglrx] total      GART = 134217728
[fglrx] free       GART = 118226944
[fglrx] max single GART = 118226944
[fglrx] total      LFB  = 260960256
[fglrx] free       LFB  = 250474496
[fglrx] max single LFB  = 250474496
[fglrx] total      Inv  = 268435456
[fglrx] free       Inv  = 268435456
[fglrx] max single Inv  = 268435456
[fglrx] total      TIM  = 0
ReiserFS: loop0: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on loop0


i don't know what all of this means. can anyone shed a little more light on this mounting filesystem business?
Back to top
View user's profile Send private message
desultory
Bodhisattva
Bodhisattva


Joined: 04 Nov 2005
Posts: 9410

PostPosted: Mon Aug 27, 2007 7:51 am    Post subject: Reply with quote

You need to modify /etc/fstab to specify ext2 instead of reiserfs for /usr/portage_volume, once that is done mount /usr/portage_volume, no need to reboot.
Back to top
View user's profile Send private message
imcominup
Apprentice
Apprentice


Joined: 07 Jan 2007
Posts: 176

PostPosted: Mon Aug 27, 2007 7:55 am    Post subject: Reply with quote

desultory wrote:
You need to modify /etc/fstab to specify ext2 instead of reiserfs for /usr/portage_volume, once that is done mount /usr/portage_volume, no need to reboot.


i figured that had something to do with it so i edited my fstab file, and tried to mount but it gave me the same error:
Code:

kumi@throne ~ $ sudo mount /usr/portage_volume
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so



should i reboot?
Back to top
View user's profile Send private message
desultory
Bodhisattva
Bodhisattva


Joined: 04 Nov 2005
Posts: 9410

PostPosted: Mon Aug 27, 2007 7:56 am    Post subject: Reply with quote

Do not reboot yet, post the contents of /etc/fstab.
Back to top
View user's profile Send private message
Akkara
Bodhisattva
Bodhisattva


Joined: 28 Mar 2006
Posts: 6702
Location: &akkara

PostPosted: Mon Aug 27, 2007 7:59 am    Post subject: Reply with quote

[Post deleted because I was too slow typing and it is now stale information]
Back to top
View user's profile Send private message
imcominup
Apprentice
Apprentice


Joined: 07 Jan 2007
Posts: 176

PostPosted: Mon Aug 27, 2007 8:01 am    Post subject: Reply with quote

desultory wrote:
Do not reboot yet, post the contents of /etc/fstab.


Code:

# /etc/fstab: static file system information.
#
# noatime turns off atimes for increased performance (atimes normally aren't
# needed; notail increases performance of ReiserFS (at the expense of storage
# efficiency).  It's safe to drop the noatime options if you want and to
# switch between notail / tail freely.
#
# The root filesystem should have a pass number of either 0 or 1.
# All other filesystems should have a pass number of 0 or greater than 1.
#
# See the manpage fstab(5) for more information.
#

# <fs>                  <mountpoint>    <type>          <opts>          <dump/pass>

# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/hda1               /boot           reiserfs        noatime,notail                          1 2
/dev/hda3               /               reiserfs        noatime,notail                          0 1
/dev/hda2               none            swap            sw                                      0 0
/dev/hda5               /tmp            reiserfs        noatime,notail,nodev,nosuid             0 0
/dev/hda6               /opt            reiserfs        noatime,notail,nodev                    0 0
/dev/hda7               /var            reiserfs        noatime,notail,nodev,nosuid             0 0
/dev/hda8               /usr            reiserfs        noatime,notail,nodev                    0 0
/dev/hda9               /home           reiserfs        noatime,notail,nodev,nosuid             0 0

/dev/cdroms/cdrom0      /mnt/cdrom      iso9660         noauto,ro       0 0
/dev/fd0                /mnt/floppy     auto            noauto          0 0
/dev/sda1               /mnt/sda1       auto            users           0 0

# NOTE: The next line is critical for boot!
proc                    /proc           proc            defaults        0 0

# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink).
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
#  use almost no memory if not populated with files)
shm                     /dev/shm        tmpfs           nodev,nosuid,noexec     0 0

/usr/portage_volume     /usr/portage    ext2    noatime,loop,notail,nodev
Back to top
View user's profile Send private message
Akkara
Bodhisattva
Bodhisattva


Joined: 28 Mar 2006
Posts: 6702
Location: &akkara

PostPosted: Mon Aug 27, 2007 8:14 am    Post subject: Reply with quote

I **think** the notail option is something specific to reiser-fs and ext2 doesn't like it. Try removing just that one option from the /usr/portage line.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum