<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.3790.4186" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT face="Courier New" color=#0000ff
size=2></FONT> </DIV>
<DIV dir=ltr align=left><SPAN class=255324916-04022008><FONT face="Courier New"
color=#0000ff size=2>I would seriously start thinking about using LVM on such a
large storage unit.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=255324916-04022008><FONT face="Courier New"
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=255324916-04022008><FONT face="Courier New"
color=#0000ff size=2>You can't use an MBR partition table on a volume that large
there is a max 2TB disk size limit and 2TB partition size limit for MBR, so you
must use GPT.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=255324916-04022008><FONT face="Courier New"
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=255324916-04022008><FONT face="Courier New"
color=#0000ff size=2>There is a real lack of reliable and easy GPT tools under
Linux, parted can read GPT partition tables, but I do not believe it can create
them AFAIK.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=255324916-04022008><FONT face="Courier New"
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=255324916-04022008><FONT face="Courier New"
color=#0000ff size=2>LVM can handle volumes of extremely large size (64-bit), so
you shouldn't run into any problems there and you can create file systems
directly in LVs of 2TB+.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=255324916-04022008><FONT face="Courier New"
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=255324916-04022008><FONT face="Courier New"
color=#0000ff size=2>-Ross</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=255324916-04022008><FONT face="Courier New"
color=#0000ff size=2></FONT></SPAN> </DIV><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> centos-bounces@centos.org
[mailto:centos-bounces@centos.org] <B>On Behalf Of </B>Rob
Lines<BR><B>Sent:</B> Monday, February 04, 2008 11:34 AM<BR><B>To:</B> CentOS
mailing list<BR><B>Subject:</B> [CentOS] Large RAID volume
issues<BR></FONT><BR></DIV>
<DIV></DIV>I have just finished creating an array on our new enclosure and our
CentOS 5 server has recognized it. It shows as the full 6tb in the LSI
configuration utility as well as when I ran fdisk:<BR><BR>[root@HOST sbin]#
fdisk /dev/sdb<BR>Note: sector size is 2048 (not 512)<BR><BR>The number of
cylinders for this disk is set to 182292.<BR>There is nothing wrong with that,
but this is larger than 1024,<BR>and could in certain setups cause problems
with:<BR>1) software that runs at boot time (e.g., old versions of LILO)<BR>2)
booting and partitioning software from other OSs<BR> (e.g., DOS
FDISK, OS/2 FDISK)<BR><BR>Command (m for help): p<BR><BR>Disk /dev/sdb: 5997.6
GB, 5997628227584 bytes<BR>255 heads, 63 sectors/track, 182292
cylinders<BR>Units = cylinders of 16065 * 2048 = 32901120
bytes<BR><BR> Device Boot
Start
End Blocks Id System<BR><BR>I
was then created a parition in fdisk and it appeared to work until I formated
it (here is the output of the formating)<BR><BR>[root@HOST ~]# mkfs -t ext2 -j
/dev/sdb1<BR>mke2fs 1.39 (29-May-2006)<BR>Filesystem label=<BR>OS type:
Linux<BR>Block size=4096 (log=2)<BR>Fragment size=4096 (log=2)<BR>195264512
inodes, 390518634 blocks<BR>19525931 blocks (5.00%) reserved for the super
user<BR>First data block=0<BR>Maximum filesystem blocks=4294967296<BR>11918
block groups<BR>32768 blocks per group, 32768 fragments per group<BR>16384
inodes per group<BR>Superblock backups stored on
blocks:<BR> 32768, 98304, 163840,
229376, 294912, 819200, 884736, 1605632,
2654208,<BR> 4096000, 7962624,
11239424, 20480000, 23887872, 71663616,
78675968,<BR> 102400000,
214990848<BR><BR>Writing inode tables: done<BR>Creating journal (32768
blocks): done<BR>Writing superblocks and filesystem accounting information:
done<BR><BR>When I did a df I got the following (only included the array
entry)<BR><BR>[root@HOST etc]# df
-h<BR>Filesystem
Size Used Avail Use% Mounted
on<BR>...<BR>/dev/sdb1
1.5T 198M 1.5T 1% /home1<BR><BR>I then tried removing
it and working with parted. <BR><BR><BR>[root@HOST etc]# parted
/dev/sdb<BR>Warning: Device /dev/sdb has a logical sector size of 2048.
Not all parts of GNU Parted support this at<BR>the moment, and the working
code is HIGHLY EXPERIMENTAL.<BR><BR>GNU Parted 1.8.1<BR>Using
/dev/sdb<BR>Welcome to GNU Parted! Type 'help' to view a list of
commands.<BR>(parted) p<BR>Error: Unable to open /dev/sdb - unrecognised disk
label.<BR>(parted) mklabel gpt<BR>*** glibc detected *** <unknown>:
double free or corruption (!prev): 0x0000000016760800 ***<BR>=======
Backtrace:
=========<BR>/lib64/libc.so.6[0x3435c6f4f4]<BR>/lib64/libc.so.6(cfree+0x8c)[0x3435c72b1c]<BR>/usr/lib64/libparted-1.8.so.0[0x3436c1a5c5]<BR>/usr/lib64/libparted-1.8.so.0[0x3436c48a54]<BR>=======
Memory map: ========<BR>00400000-00410000 r-xp 00000000 08:05
130761
/sbin/parted<BR>00610000-00611000 rw-p 00010000 08:05
130761
/sbin/parted<BR>00611000-00612000 rw-p 00611000 00:00 0<BR>00810000-00812000
rw-p 00010000 08:05
130761
/sbin/parted<BR>1673d000-1677f000 rw-p 1673d000 00:00
0<BR>3435800000-343581a000 r-xp 00000000 08:05
4765445
/lib64/ld-<A href="http://2.5.so">2.5.so</A><BR>3435a19000-3435a1a000 r--p
00019000 08:05
4765445
/lib64/ld-<A href="http://2.5.so">2.5.so</A><BR>3435a1a000-3435a1b000 rw-p
0001a000 08:05
4765445
/lib64/ld-<A href="http://2.5.so">2.5.so</A><BR>3435c00000-3435d46000 r-xp
00000000 08:05
4765452
/lib64/libc-<A href="http://2.5.so">2.5.so</A><BR>3435d46000-3435f46000 ---p
00146000 08:05
4765452
/lib64/libc-<A href="http://2.5.so">2.5.so</A><BR>3435f46000-3435f4a000 r--p
00146000 08:05
4765452
/lib64/libc-<A href="http://2.5.so">2.5.so</A><BR>3435f4a000-3435f4b000 rw-p
0014a000 08:05
4765452
/lib64/libc-<A href="http://2.5.so">2.5.so</A><BR>3435f4b000-3435f50000 rw-p
3435f4b000 00:00 0<BR>3436000000-3436013000 r-xp 00000000 08:05
4765602
/lib64/libdevmapper.so.1.02<BR>3436013000-3436213000 ---p 00013000 08:05
4765602
/lib64/libdevmapper.so.1.02<BR>3436213000-3436215000 rw-p 00013000 08:05
4765602
/lib64/libdevmapper.so.1.02<BR>3436400000-3436402000 r-xp 00000000 08:05
4765458
/lib64/libdl-<A href="http://2.5.so">2.5.so</A><BR>3436402000-3436602000 ---p
00002000 08:05
4765458
/lib64/libdl-<A href="http://2.5.so">2.5.so</A><BR>3436602000-3436603000 r--p
00002000 08:05
4765458
/lib64/libdl-<A href="http://2.5.so">2.5.so</A><BR>3436603000-3436604000 rw-p
00003000 08:05
4765458
/lib64/libdl-<A href="http://2.5.so">2.5.so</A><BR>3436800000-3436802000 r-xp
00000000 08:05
4765478
/lib64/libuuid.so.1.2<BR>3436802000-3436a02000 ---p 00002000 08:05
4765478
/lib64/libuuid.so.1.2<BR>3436a02000-3436a03000 rw-p 00002000 08:05
4765478
/lib64/libuuid.so.1.2<BR>3436c00000-3436c5c000 r-xp 00000000 08:05
464724
/usr/lib64/libparted-1.8.so.0.0.
1<BR>3436c5c000-3436e5b000 ---p 0005c000 08:05
464724
/usr/lib64/libparted-1.8.so.0.0.
1<BR>3436e5b000-3436e5f000 rw-p 0005b000 08:05
464724
/usr/lib64/libparted-1.8.so.0.0.
1<BR>3436e5f000-3436e60000 rw-p 3436e5f000 00:00 0<BR>3437000000-3437035000
r-xp 00000000 08:05
463236
/usr/lib64/libreadline.so.5.1<BR>3437035000-3437234000 ---p 00035000 08:05
463236
/usr/lib64/libreadline.so.5.1<BR>3437234000-343723c000 rw-p 00034000 08:05
463236
/usr/lib64/libreadline.so.5.1<BR>343723c000-343723d000 rw-p 343723c000 00:00
0<BR>343b000000-343b00d000 r-xp 00000000 08:05
4765466
/lib64/libgcc_s-4.1.2-20070626.s
o.1<BR>343b00d000-343b20d000 ---p 0000d000 08:05
4765466
/lib64/libgcc_s-4.1.2-20070626.s
o.1<BR>343b20d000-343b20e000 rw-p 0000d000 08:05
4765466
/lib64/libgcc_s-4.1.2-20070626.s
o.1<BR>343c000000-343c03b000 r-xp 00000000 08:05
4765743
/lib64/libsepol.so.1<BR>343c03b000-343c23b000 ---p 0003b000 08:05
4765743
/lib64/libsepol.so.1<BR>343c23b000-343c23c000 rw-p 0003b000 08:05
4765743
/lib64/libsepol.so.1<BR>343c23c000-343c246000 rw-p 343c23c000 00:00
0<BR>343c400000-343c415000 r-xp 00000000 08:05
4765744
/lib64/libselinux.so.1<BR>343c415000-343c615000 ---p 00015000 08:05
4765744
/lib64/libselinux.so.1<BR>343c615000-343c617000 rw-p 00015000 08:05
4765744
/lib64/libselinux.so.1<BR>343c617000-343c618000 rw-p 343c617000 00:00
0<BR>3448e00000-3448e4e000 r-xp 00000000 08:05
464701
/usr/lib64/libncurses.so.5.5<BR>3448e4e000-344904e000 ---p 0004e000 08:05
464701
Aborted<BR><BR>Any suggestions or direction would be appreciated.<BR><BR>Thank
you,<BR>Rob<BR><BR></BLOCKQUOTE>
<P></P>
<HR WIDTH="100%">
This e-mail, and any attachments thereto, is intended only for use by
the addressee(s) named herein and may contain legally privileged
and/or confidential information. If you are not the intended recipient
of this e-mail, you are hereby notified that any dissemination,
distribution or copying of this e-mail, and any attachments thereto,
is strictly prohibited. If you have received this e-mail in error,
please immediately notify the sender and permanently delete the
original and any copy or printout thereof.
</BODY></HTML>