greyhole and 3tb drives

[rcrh]

OK, now I really really hate to do this because I'm moving into the pita arena but can you offer some help in getting rid of the GPT information on my drive?

I keep getting this info from fdisk -l

WARNING: GPT (GUID Partition Table) detected on '/dev/sde'! The util fdisk doesn't support GPT. Use GNU Parted.

Note: sector size is 4096 (not 512)

Disk /dev/sde: 3000.6 GB, 3000592977920 bytes
255 heads, 63 sectors/track, 45600 cylinders, total 732566645 sectors
Units = sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000001

I've tried fdisk and it appeared to work but when I reboot I got the above.

I moved the drive to my win7 machine and deleted the partition and came back to Amahi. The reboot gave me the above.

I went back to win7, deleted the partition, created an NTFS partition, came back to Amahi, used gpart and deleted the NTFS partition and created new ext4 partitions. The reboot gave me the above!

I'm completely stumped. I know I have to get rid of the GPT info before I can move forward but I just can't figure it out. PARTED -h didn't give me any useful info either.

I hope you can help get be back on track.

Thanks yet again.
Richard.

[rcrh]

So, splitting the drive into two partitions worked. I don't know why, but I guess I don't care.

However, fdisk -l still shows the error message I reported about. Should I be concerned with this error? At some point am I going to reboot and find that the drive has reverted back to 3tb and I've lost all of the data on it?

Bigfoot65, thanks one last time for all of your help with this.

[ListerD]

I'm having the same issue. drive15 is the drive in question. Running a stats shows the following:

Storage Pool
Total - Used = Free + Trash = Possible
/var/hda/files/gh: 1814G - 1626G = 186G + 1G = 187G
/var/hda/files/drives/drive2/gh: 917G - 732G = 184G + 4G = 189G
/var/hda/files/drives/drive4/gh: 1834G - 1647G = 185G + 7G = 191G
/var/hda/files/drives/drive8/gh: 1834G - 1657G = 175G + 0G = 175G
/var/hda/files/drives/drive11/gh: 1375G - 1189G = 185G + 1G = 186G
/var/hda/files/drives/drive13/gh: 1834G - 1651G = 181G + 1G = 181G
/var/hda/files/drives/drive15/gh: 2751G - 0G = 2611G + 0G = 2611G
==========================================
Total: 12358G - 8502G = 3706G + 14G = 3720G

The log when balancing shows the following:

Nov 12 10:25:32 7 balance: Drives with available space: /var/hda/files/drives/drive15/gh (2.54TB avail) - /var/hda/files/gh (176GB avail) - /var/hda/files/drives/drive4/gh (175GB avail) - /var/hda/files/drives/drive11/gh (175GB avail) - /var/hda/files/drives/drive2/gh (174GB avail) - /var/hda/files/drives/drive13/gh (171GB avail) - /var/hda/files/drives/drive8/gh (165GB avail)
Nov 12 10:25:32 7 balance: Target drive: /var/hda/files/drives/drive15/gh (-1.46TB available)
Nov 12 10:25:32 7 balance: Moving this file wouldn't help balancing available space. Skipping.

df -h reports:

Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_amahi-lv_root
14G 4.0G 8.8G 31% /
tmpfs 1002M 448K 1001M 1% /dev/shm
/dev/sda1 485M 56M 404M 13% /boot
/dev/mapper/vg_amahi-lv_home
3.9G 118M 3.6G 4% /home
/dev/sda3 1.8T 1.6T 187G 90% /var/hda/files
/dev/sdb1 917G 732G 185G 80% /var/hda/files/drives/drive2
/dev/sdg1 1.8T 1.7T 185G 90% /var/hda/files/drives/drive4
/dev/sdc1 1.8T 1.7T 175G 91% /var/hda/files/drives/drive8
/dev/sdd1 1.4T 1.2T 185G 87% /var/hda/files/drives/drive11
/dev/sde1 1.8T 1.7T 181G 91% /var/hda/files/drives/drive13
/dev/sdh1 2.7T 202M 2.6T 1% /var/hda/files/drives/drive15

As a result of the incorrect target drive space being reported, no files are being transferred to the 3TB drive. Any ideas on why it would be reporting the negative space only during one aspect of balancing, or where that target drive space value is coming from?

[rcrh]

ListerD

I'm going to keep monitoring this post to see if there's a resolution but in the mean time you might want to consider repartitioning the drive into two partitions and then add both to the pool. It work for me.

Best of luck.

[ListerD]

rcrh,

Been off the board for a while as I've been building a new PC and repurposing my old one as a new Amahi server (headless no more!). Still working on adding the pooled drives back, but hopefully that will be done Wednesday night

Sorry if this is a stupid question, but by partitioning, will greyhole see each partition as a separate drive, or does it recognize that they are the same physical device? My concern is with replicating files and having both copy1 and copy2 on 2 different partitions on the same physical disk.

Thx!

[rcrh]

rcrh,
Sorry if this is a stupid question, but by partitioning, will greyhole see each partition as a separate drive, or does it recognize that they are the same physical device? My concern is with replicating files and having both copy1 and copy2 on 2 different partitions on the same physical disk.
Thx!

Holy smackers! I hadn't thought of that. Dang! Dang! Dang!

I'm going to have to do some checking tomorrow to see where files are falling.

[bigfoot65]

I believe it sees it as separate drives per say. I had mine set up that way at one time. Now I have actual separate drives.

[rcrh]

I believe it sees it as separate drives per say. I had mine set up that way at one time. Now I have actual separate drives.

Well that would be terrible as it would mean I don't have effective duplication.

It also means I have to go back to trying to solve my original issue with the 3TB drive.

Any other thoughts on that problem?

[bigfoot65]

I would think having 2 copies of a file on the same drive would be effective, just not efficient

You might wanna clarify if that is how it works and I am not 100% sure.

[radioz]

The problem is if the drive dies, both your copies are gone.