Hi David,
I figured it out. I used the msdos label in parted to while creating
partitions, and that is why they got all screwed up. I then switched to
"gpt" and now everything works like a charm!!!!
Thanks very much for all your help.
Nikhil
-----Original Message-----
From: David Chinner [mailto:dgc@xxxxxxx]
Sent: Thursday, September 21, 2006 7:14 PM
To: Nikhil Kulkarni
Cc: David Chinner; xfs@xxxxxxxxxxx
Subject: Re: xfs_read_buf error 5.
On Thu, Sep 21, 2006 at 05:45:32PM -0700, Nikhil Kulkarni wrote:
> Hi David,
>
> Hi David,
>
> Thanks for your prompt response, I really appreciate it!!! I made a
> major tying mistake in describing the initial size of the partitions.
We
> are having issues when we assign a size > 2TB and not 2GB. I'm sorry
> about the typo.
I was wondering about that ;)
> Here are the 2 /proc/partition files:
>
> This is the one where the partition size is 3.5T
>
> [nikhil@nkulkarni tmp]$ more xfs-log-3.5T
> [root@ssimppi7 log]# cat /proc/partitions
> major minor #blocks name
>
> 8 0 4093902848 sda
> 8 1 1436513398 sda1
That says it's only 1.4TB...
> This is the one where the partition size is 2TB:
>
> [nikhil@nkulkarni tmp]$ more xfs-log-2T
> root@ssimppi7 log]# cat /proc/partitions
> major minor #blocks name
>
> 8 0 4093902848 sda
> 8 1 2047998298 sda1
And that is 2TB.
> I think you are right. The partitions are not set up correctly.
>
> Do you know on a 2.5 kernel on a 32 bit operating system, which tool
can
> be used to setup partitions for sizes up to 4TB or 8TB?
> fdisk on a 32 bit os does not work correctly. I thought parted worked
> but apparently it does not either.
Did you build your kernel with CONFIG_LBD=y? (Block layer option)
This is the option that allows >2TB block devices on 32 bit kernels...
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
|