Maverick on Weybridge + WD2.5THDD

[manoj.iyer at canonical.com]

Harry,

I started a stress test this afternoon and it is still going, the test 
spawns 32768 threads, which is little over 1/2 max threads, and each 
thread write/remove 1GB files (in a loop). Hopefully some of these threads 
will write close to the end of the disk as well. The HDD is warm to the 
touch, hopefully I wont fry the WD drive ;)


Cheers
--- manjo

On Thu, 7 Oct 2010, Hsiung, Harry L wrote:

> I had done an installation on maverick meerkat daily build amd64.iso from 9/10/10 for IDF (sept 14th). I did not have any problems and could see all of the disk. The official Meerkat build (before sept 11th) appears to have UEFI install missing.
>
> If you have any disk utilities to test the filesystem (all 2.5tb or 3tb) would like to know if the file system is really functional all they way out to the end of the disk.
>
> Could do the brute force thing of copying files until I fill the disk up but it is really time consuming. Checking to see if the filesystem is corrupt is still a question in my mind (does fsck check this for disks and file systems >2.2 tb)?
>
> Harry Hsiung (熊海霖)
> Intel Corp.
> SSG PSI Tiano/EFI TME
> Dupont WA DP2-420
> office 253-371-5381
> cell 360-870-2141
>
>
> -----Original Message-----
> From: Manoj Iyer [mailto:manoj.iyer at canonical.com]
> Sent: Thursday, October 07, 2010 11:31 AM
> To: Bob Griswold; Hsiung, Harry L
> Cc: Ubuntu Kernel Team
> Subject: Maverick on Weybridge + WD2.5THDD
>
>
> Harry/Bob,
>
> I was able to install Maverick on the Weybridge with the 2.5T HDD shipped
> to me from WD by Bob. Installed from CD in UEFI mode.
>
>
> Disk /dev/sda1: 18 MB, 18874368 bytes
> 255 heads, 63 sectors/track, 2 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 4096 bytes
> I/O size (minimum/optimal): 4096 bytes / 4096 bytes
> Disk identifier: 0x00000000
>
>      Device Boot      Start         End      Blocks   Id  System
>
>
> Disk /dev/sda2: 2494.4 GB, 2494448009216 bytes
> 255 heads, 63 sectors/track, 303266 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 4096 bytes
> I/O size (minimum/optimal): 4096 bytes / 4096 bytes
> Disk identifier: 0x00000000
>
> Looks ok to me at first glance, if you guys notice anything abnormal
> please share it with me.
>
>
> Cheers
> --- manjo
>