<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Bryan J. Smith wrote:
<blockquote
cite="mid20051109175253.8209.qmail@web34105.mail.mud.yahoo.com"
type="cite">
<pre wrap="">kadafax <a class="moz-txt-link-rfc2396E" href="mailto:kadafax@gmail.com"><kadafax@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Thanks for reply Bryan,
in fact since the mounted FS is for backup purpose only,
it's not a big deal to un-mount it (far better than
disabling the ldap service with a reboot). I've checked
google and the result it gives seems to be too
heavy for this production server (new scsi driver etc.). So
if you have a solution who is working on un-mounted volume,
I'm very interrested.
PS: The SAN is an AX100sc from EMC. The host adapter is a
QLA200 from QLogic. OS: CentOS 4.2
</pre>
</blockquote>
<pre wrap=""><!---->
If all volumes are unmounted, then you can simply remove the
driver and modprobe it again.
E.g.,
# /sbin/rmmod qla2200
# /sbin/modprobe qla2200
I'm assuming your /etc/modprobe.conf file has all options
(SAN paths, etc...) for the card defined.
Once that is done, your /dev/sdb device should be updated to
reflect the new geometry of the storage. Just add the new
space as a new, physical volume, add it to your existing
volume group, etc...
</pre>
</blockquote>
Quite there: the new size is reflected...but the disks (I've got two
virtual disks from the SAN, who are seen like scsi disk by the system)
are now described as /dev/sdd and /dev/sde (initialy /dev/sdb and sdc)
(below output from a "fdisk -l", the disc which grew is initialy sdb).
And a "pvdisplay" do not see any new physical extents available
(perhaps I'm missing something on this, I'm totally new from this and
way long to be totally cool with it):<br>
---<br>
<br>
* before the rmmod/modprobe (see /dev/sdb):<br>
---<br>
<small>[root@X install]# fdisk -l<br>
<br>
Disk /dev/sda: 146.6 GB, 146695782400 bytes<br>
255 heads, 63 sectors/track, 17834 cylinders<br>
Units = cylinders of 16065 * 512 = 8225280 bytes<br>
<br>
Device Boot Start End Blocks Id System<br>
/dev/sda1 * 1 13 104391 83 Linux<br>
/dev/sda2 14 17834 143147182+ 8e Linux LVM<br>
<br>
Disk /dev/sdb: 700.0 GB, 700079669248 bytes<br>
255 heads, 63 sectors/track, 85113 cylinders<br>
Units = cylinders of 16065 * 512 = 8225280 bytes<br>
<br>
Disk /dev/sdb doesn't contain a valid partition table<br>
<br>
Disk /dev/sdc: 233.0 GB, 233001975808 bytes<br>
255 heads, 63 sectors/track, 28327 cylinders<br>
Units = cylinders of 16065 * 512 = 8225280 bytes<br>
<br>
Disk /dev/sdc doesn't contain a valid partition table</small><br>
---<br>
<br>
After:<br>
<br>
---<br>
<small>[root@X install]# fdisk -l<br>
<br>
Disk /dev/sda: 146.6 GB, 146695782400 bytes<br>
255 heads, 63 sectors/track, 17834 cylinders<br>
Units = cylinders of 16065 * 512 = 8225280 bytes<br>
<br>
Device Boot Start End Blocks Id System<br>
/dev/sda1 * 1 13 104391 83 Linux<br>
/dev/sda2 14 17834 143147182+ 8e Linux LVM<br>
<br>
Disk /dev/sdd: 933.0 GB, 933081645056 bytes<br>
255 heads, 63 sectors/track, 113440 cylinders<br>
Units = cylinders of 16065 * 512 = 8225280 bytes<br>
<br>
Disk /dev/sdd doesn't contain a valid partition table<br>
<br>
Disk /dev/sde: 233.0 GB, 233001975808 bytes<br>
255 heads, 63 sectors/track, 28327 cylinders<br>
Units = cylinders of 16065 * 512 = 8225280 bytes<br>
<br>
Disk /dev/sde doesn't contain a valid partition table</small><br>
---<br>
Should I be worried about the "non-valid partition" table message? I
can use the LV (mount and work with files), so I don't know if it is a
problem. Maybe the fact that there is no partition table for fdisk is
why I can't make it grow? I mean, maybe I should have create first one
partition (type LVM), then create a second one with the extra size ? <br>
Here is what I've done to create the logical volume:<br>
---<br>
<small>[root@X ~]# pvcreate /dev/sdb<br>
[root@X ~]# vgcreate VG-B /dev/sdb<br>
[root@X ~]# lvcreate -l 166911 VG-B -n LV-B <br>
// Note: 166911 is the maximum number of physical extents available
before the grow<br>
[root@X ~]# mkfs.ext3 /dev/VG-B/LV-B</small><br>
--- <br>
from there I could use the volume.<br>
<br>
---<br>
<br>
<small>[root@onyx install]# pvdisplay <br>
--- Physical volume ---<br>
PV Name /dev/sde<br>
VG Name VG-C<br>
PV Size 217.00 GB / not usable 0 <br>
Allocatable yes (but full)<br>
PE Size (KByte) 4096<br>
Total PE 55551<br>
Free PE 0<br>
Allocated PE 55551<br>
PV UUID w3Q4hA-ALnz-4UuH-fdBB-FGOT-Rn2t-4iG2Vv<br>
<br>
--- Physical volume ---<br>
PV Name /dev/sdd<br>
VG Name VG-B<br>
PV Size 652.00 GB / not usable 0 <br>
Allocatable yes (but full)<br>
PE Size (KByte) 4096<br>
Total PE 166911<br>
Free PE 0<br>
Allocated PE 166911<br>
PV UUID AFcoa6-6eJl-AAd3-G0Vt-OTXR-niPn-3bTLXu<br>
<br>
--- Physical volume ---<br>
PV Name /dev/sda2<br>
VG Name VolGroup00<br>
PV Size 136.50 GB / not usable 0 <br>
Allocatable yes <br>
PE Size (KByte) 32768<br>
Total PE 4368<br>
Free PE 1<br>
Allocated PE 4367<br>
PV UUID OjQEXi-u3F8-wCXO-1eZY-W2j0-iZyG-5PwwnB</small><br>
----<br>
<br>
<br>
</body>
</html>