Re: [gentoo-user] LVM2 Problems

2006-05-11 Thread Barny M
Boyd Stephen Smith Jr. wrote:
 Then why do we see zoom here?

Sorry zoom is actually cont. For some reasons I good the word zoom
in here :-(


 Also, be /very/ careful with upgrading LVM / device-mapper. 

Sure ;-)

Back to my last question. Any thoughts how to get this fixed without
remote hand (liveCD) only console ?

Thanks

~Barny

-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] LVM2 Problems

2006-05-11 Thread Boyd Stephen Smith Jr.
On Thursday 11 May 2006 06:06, Barny M [EMAIL PROTECTED] wrote about 'Re: 
[gentoo-user] LVM2 Problems':
 Boyd Stephen Smith Jr. wrote:
  Then why do we see zoom here?

 Sorry zoom is actually cont. For some reasons I good the word zoom
 in here :-(

Ah, well if all the messages say cont it's probably not a metadata 
problem.  Is dm-mod actually getting loaded?  Also, you may be able to use 
lvdisplay to determine the major/minor numbers of the block device you 
need to create and then create it by hand.  That may or may not work.

  Also, be /very/ careful with upgrading LVM / device-mapper.

 Sure ;-)

 Back to my last question. Any thoughts how to get this fixed without
 remote hand (liveCD) only console ?

Without /usr portage isn't going to work, so any kernel/dm/lvm changes will 
have to be without portage -- and might leave a little bit of cruft on 
your system.

If you are fine with that... quickpkg or buildpkg dm/lvm on another 
computer (mkae sure you CFLAGS are appropriately generic), copy over, and 
just install with tar.  Or build a different kernel, copy over to boot, 
modify grub/re-run lilo and go.

-- 
If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability.
-- Gentoo Developer Ciaran McCreesh


pgpWueb9wbHz3.pgp
Description: PGP signature


Re: [gentoo-user] LVM2 Problems

2006-05-10 Thread Barny M
Richard Fish wrote:
 On 5/9/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
 
 vgchange -a y
   device-mapper: deps ioctl failed: Invalid argument
   _deps: task run failed for (254:0)
   Failed to add device (254:0) to dtree
 
 
 My guess is a conflict between the device-mapper version and your
 kernel.  2.6.7 is quite ancient, and looking through
 /usr/share/doc/device-mapper-1.02.05/WHATS_NEW.gz, there were a lot of
 changes to how the device nodes are created in the last couple of
 years.  Possibly one of those changes broke backwards compatibility.
 
 -Richard
 

I forgot one important bit here to mention, at least to me ;-) The
server is miles away from my office, all I got is console access..

The other (older) kernel will not boot up properly either. Firering up
lvm and typing help, show various commands, which I am not familar with.

Does anyone see any option to get the fs back up just using console and
no remote hands ?

Thanks.

~Barny
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] LVM2 Problems

2006-05-10 Thread Boyd Stephen Smith Jr.
On Tuesday 09 May 2006 10:40, [EMAIL PROTECTED] wrote about '[gentoo-user] 
LVM2 Problems':
 I recently synced my Gentoo (2.6.7-gentoo-r13) and after emerging
 updated ebuilds, sure lvm2 was one of them and a reboot I lost my
 mounted fs.

 /dev/cont/swap  noneswapsw
   
   PV /dev/hda3   VG cont   lvm2 [111.23 GB / 6.74 GB free]
  
   Found volume group cont using metadata type lvm2


So, it would seem that your volume group is named cont, yes?

   8 logical volume(s) in volume group zoom now active
 

Then why do we see zoom here?

Clearly, there is some metadata that doesn't agree.  Try a vgcfgbackup and 
vgcfgrestore to get your metadata in sync.  If that doesn't fix things 
try:
vgchange -an cont zoom
vgrename cont zoom
vgrename zoom cont

Also, be /very/ careful with upgrading LVM / device-mapper.  I've certainly 
had issues where old LVM wouldn't work with new dm or new LVM wouldn't 
work with old dm.  (But, I have LVM dynamically linked instead of the 
Gentoo default of statically.)

Oh, BTW, if it /is/ a dm/kernel conflict, and you have LVM statically 
linked, you'll have to recompile it *after* you've changed to a dm 
supported by your kernel (if you change you kernel, but not your dm, this 
won't apply).  Otherwise, it won't use your new dm version.  Such is the 
benefit and detriment of static linking.

-- 
If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability.
-- Gentoo Developer Ciaran McCreesh


pgpLsJcKTB2o3.pgp
Description: PGP signature


Re: [gentoo-user] LVM2 problems

2006-05-10 Thread Boyd Stephen Smith Jr.
On Tuesday 09 May 2006 12:40, Barny M [EMAIL PROTECTED] wrote 
about '[gentoo-user] LVM2 problems':
 Any further suggestions how to troubleshoot or fix the issue ?

See my answer to your previous post.  Also, gmail doesn't show you your own 
messages.

-- 
If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability.
-- Gentoo Developer Ciaran McCreesh


pgp2bju5VCxIc.pgp
Description: PGP signature


[gentoo-user] LVM2 Problems

2006-05-09 Thread bm2600
Hi,

I recently synced my Gentoo (2.6.7-gentoo-r13) and after emerging
updated ebuilds, sure lvm2 was one of them and a reboot I lost my
mounted fs.

Fortunately I do not have / (root) under LVM however all efforts so far
haven't brought my fs back:

# /etc/fstab: static file system information.
# $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/fstab,v 1.14
2003/10/13 20:03:38 azarah Exp $
#
# 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 and tail freely.

# fs  mountpointtype  opts
dump/pass

# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/hda1   /boot   ext2noauto,noatime
0 0
/dev/hda2   /   reiserfsnoatime
0 0
/dev/cont/swap  noneswapsw
0 0
/dev/cont/usr   /usrreiserfsnoatime
0 0
/dev/cont/var   /varreiserfsnoatime
0 0
/dev/cont/home  /home   reiserfsnoatime
0 0
/dev/cont/tmp   /tmpreiserfsnoatime
0 0
/dev/cont/var-log   /var/logreiserfsnoatime
0 0
/dev/cont/var-www   /var/wwwreiserfsnoatime
0 0
/dev/cdroms/cdrom0  /mnt/cdrom  iso9660 noauto,ro
0 0
#/dev/fd0   /mnt/floppy autonoauto
0 0

# NOTE: The next line is critical for boot!
none/proc   procdefaults
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)
# Adding the following line to /etc/fstab should take care of this:

none/dev/shmtmpfs   defaults
0 0


df -h
FilesystemSize  Used Avail Use% Mounted on
/dev/hda2 479M   80M  399M  17% /
none


pvscan
  PV /dev/hda3   VG cont   lvm2 [111.23 GB / 6.74 GB free]
  Total: 1 [111.23 GB] / in use: 1 [111.23 GB] / in no VG: 0 [0   ]

vgscan
  Reading all physical volumes.  This may take a while...
  Found volume group cont using metadata type lvm2

vgchange -a y
  device-mapper: deps ioctl failed: Invalid argument
  _deps: task run failed for (254:0)
  Failed to add device (254:0) to dtree
  device-mapper: deps ioctl failed: Invalid argument
  _deps: task run failed for (254:1)
  Failed to add device (254:1) to dtree
  device-mapper: deps ioctl failed: Invalid argument
  _deps: task run failed for (254:2)
  Failed to add device (254:2) to dtree
  device-mapper: deps ioctl failed: Invalid argument
  _deps: task run failed for (254:3)
  Failed to add device (254:3) to dtree
  device-mapper: deps ioctl failed: Invalid argument
  _deps: task run failed for (254:4)
  Failed to add device (254:4) to dtree
  device-mapper: deps ioctl failed: Invalid argument
  _deps: task run failed for (254:5)
  Failed to add device (254:5) to dtree
  device-mapper: deps ioctl failed: Invalid argument
  _deps: task run failed for (254:6)
  Failed to add device (254:6) to dtree
  device-mapper: deps ioctl failed: Invalid argument
  _deps: task run failed for (254:7)
  Failed to add device (254:7) to dtree
  8 logical volume(s) in volume group zoom now active
  248M 0  248M   0% /dev/shm

Any further suggestions how to troubleshoot or fix the issue ?

~Barny




-- 
gentoo-user@gentoo.org mailing list



[gentoo-user] LVM2 problems

2006-05-09 Thread Barny M
Hi,

I recently synced my Gentoo (2.6.7-gentoo-r13) and after emerging
updated ebuilds, sure lvm2 was one of them and a reboot I lost my
mounted fs.

Fortunately I do not have / (root) under LVM however all efforts so far
haven't brought my fs back:

# /etc/fstab: static file system information.
# $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/fstab,v 1.14
2003/10/13 20:03:38 azarah Exp $
#
# 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 and tail freely.

# fs  mountpointtype  opts
dump/pass

# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/hda1   /boot   ext2noauto,noatime
0 0
/dev/hda2   /   reiserfsnoatime
0 0
/dev/cont/swap  noneswapsw
0 0
/dev/cont/usr   /usrreiserfsnoatime
0 0
/dev/cont/var   /varreiserfsnoatime
0 0
/dev/cont/home  /home   reiserfsnoatime
0 0
/dev/cont/tmp   /tmpreiserfsnoatime
0 0
/dev/cont/var-log   /var/logreiserfsnoatime
0 0
/dev/cont/var-www   /var/wwwreiserfsnoatime
0 0
/dev/cdroms/cdrom0  /mnt/cdrom  iso9660 noauto,ro
0 0
#/dev/fd0   /mnt/floppy autonoauto
0 0

# NOTE: The next line is critical for boot!
none/proc   procdefaults
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)
# Adding the following line to /etc/fstab should take care of this:

none/dev/shmtmpfs   defaults
0 0


df -h
FilesystemSize  Used Avail Use% Mounted on
/dev/hda2 479M   80M  399M  17% /
none


pvscan
  PV /dev/hda3   VG cont   lvm2 [111.23 GB / 6.74 GB free]
  Total: 1 [111.23 GB] / in use: 1 [111.23 GB] / in no VG: 0 [0   ]

vgscan
  Reading all physical volumes.  This may take a while...
  Found volume group cont using metadata type lvm2

vgchange -a y
  device-mapper: deps ioctl failed: Invalid argument
  _deps: task run failed for (254:0)
  Failed to add device (254:0) to dtree
  device-mapper: deps ioctl failed: Invalid argument
  _deps: task run failed for (254:1)
  Failed to add device (254:1) to dtree
  device-mapper: deps ioctl failed: Invalid argument
  _deps: task run failed for (254:2)
  Failed to add device (254:2) to dtree
  device-mapper: deps ioctl failed: Invalid argument
  _deps: task run failed for (254:3)
  Failed to add device (254:3) to dtree
  device-mapper: deps ioctl failed: Invalid argument
  _deps: task run failed for (254:4)
  Failed to add device (254:4) to dtree
  device-mapper: deps ioctl failed: Invalid argument
  _deps: task run failed for (254:5)
  Failed to add device (254:5) to dtree
  device-mapper: deps ioctl failed: Invalid argument
  _deps: task run failed for (254:6)
  Failed to add device (254:6) to dtree
  device-mapper: deps ioctl failed: Invalid argument
  _deps: task run failed for (254:7)
  Failed to add device (254:7) to dtree
  8 logical volume(s) in volume group zoom now active
  248M 0  248M   0% /dev/shm

Any further suggestions how to troubleshoot or fix the issue ?

~Barny
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] LVM2 Problems

2006-05-09 Thread Jure Varlec
I've never seen this issue, so I may not be the right person to give advice 
here. But at a glance, it looks like lvm and device-mapper are incompatible 
or something similar. If I were in your place I would try differrent versions 
of lvm2, device-mapper and/or kernel.

FYI, my configuration works with kernel 2.6.16-r1,
device-mapper 1.02.03 and lvm2 2.02.05.

On Tuesday 09 May 2006 17:40, [EMAIL PROTECTED] wrote:
 Hi,

 I recently synced my Gentoo (2.6.7-gentoo-r13) and after emerging
 updated ebuilds, sure lvm2 was one of them and a reboot I lost my
 mounted fs.

 Fortunately I do not have / (root) under LVM however all efforts so far
 haven't brought my fs back:

 # /etc/fstab: static file system information.
 # $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/fstab,v 1.14
 2003/10/13 20:03:38 azarah Exp $
 #
 # 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 and tail freely.

 # fs  mountpointtype  opts
 dump/pass

 # NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
 /dev/hda1   /boot   ext2noauto,noatime
 0 0
 /dev/hda2   /   reiserfsnoatime
 0 0
 /dev/cont/swap  noneswapsw
 0 0
 /dev/cont/usr   /usrreiserfsnoatime
 0 0
 /dev/cont/var   /varreiserfsnoatime
 0 0
 /dev/cont/home  /home   reiserfsnoatime
 0 0
 /dev/cont/tmp   /tmpreiserfsnoatime
 0 0
 /dev/cont/var-log   /var/logreiserfsnoatime
 0 0
 /dev/cont/var-www   /var/wwwreiserfsnoatime
 0 0
 /dev/cdroms/cdrom0  /mnt/cdrom  iso9660 noauto,ro
 0 0
 #/dev/fd0   /mnt/floppy autonoauto
 0 0

 # NOTE: The next line is critical for boot!
 none/proc   procdefaults
 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)
 # Adding the following line to /etc/fstab should take care of this:

 none/dev/shmtmpfs   defaults
 0 0


 df -h
 FilesystemSize  Used Avail Use% Mounted on
 /dev/hda2 479M   80M  399M  17% /
 none


 pvscan
   PV /dev/hda3   VG cont   lvm2 [111.23 GB / 6.74 GB free]
   Total: 1 [111.23 GB] / in use: 1 [111.23 GB] / in no VG: 0 [0   ]

 vgscan
   Reading all physical volumes.  This may take a while...
   Found volume group cont using metadata type lvm2

 vgchange -a y
   device-mapper: deps ioctl failed: Invalid argument
   _deps: task run failed for (254:0)
   Failed to add device (254:0) to dtree
   device-mapper: deps ioctl failed: Invalid argument
   _deps: task run failed for (254:1)
   Failed to add device (254:1) to dtree
   device-mapper: deps ioctl failed: Invalid argument
   _deps: task run failed for (254:2)
   Failed to add device (254:2) to dtree
   device-mapper: deps ioctl failed: Invalid argument
   _deps: task run failed for (254:3)
   Failed to add device (254:3) to dtree
   device-mapper: deps ioctl failed: Invalid argument
   _deps: task run failed for (254:4)
   Failed to add device (254:4) to dtree
   device-mapper: deps ioctl failed: Invalid argument
   _deps: task run failed for (254:5)
   Failed to add device (254:5) to dtree
   device-mapper: deps ioctl failed: Invalid argument
   _deps: task run failed for (254:6)
   Failed to add device (254:6) to dtree
   device-mapper: deps ioctl failed: Invalid argument
   _deps: task run failed for (254:7)
   Failed to add device (254:7) to dtree
   8 logical volume(s) in volume group zoom now active
   248M 0  248M   0% /dev/shm

 Any further suggestions how to troubleshoot or fix the issue ?

 ~Barny


pgpBxLT72Rqdu.pgp
Description: PGP signature


Re: [gentoo-user] LVM2 Problems

2006-05-09 Thread Richard Fish

On 5/9/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

vgchange -a y
  device-mapper: deps ioctl failed: Invalid argument
  _deps: task run failed for (254:0)
  Failed to add device (254:0) to dtree


My guess is a conflict between the device-mapper version and your
kernel.  2.6.7 is quite ancient, and looking through
/usr/share/doc/device-mapper-1.02.05/WHATS_NEW.gz, there were a lot of
changes to how the device nodes are created in the last couple of
years.  Possibly one of those changes broke backwards compatibility.

-Richard

--
gentoo-user@gentoo.org mailing list