similar to: CentOS 5 32bit and 3Tbyte drives

For close to the last decade or so, I've been developing on OS X and then porting to LINUX. I know there are those who object to this approach, but it works for me. However I noticed that when porting my exception example to LINUX, which involved adding a whopping -rdynamic to the build line, there were technologies missing from my gcc and LINUX installation as compared to what is on OS X

Just installed CentOS 5.1 on VMware ESX and am attempting to play with the newly added tick_divider feature. It doesn't seem to be making any difference in the number of timer interrupts though. I set tick_divider=10 which should reduce the number of timer interrupts to 100. I wrote a nasty little scripts that queries /proc/interrupts every 1 second and still see an increase each second in

On 01/10/2010 03:09 PM, Garrison Venn wrote: > For close to the last decade or so, I've been developing on OS X and then porting to LINUX. I know there are those who object > to this approach, but it works for me. However I noticed that when porting my exception example to LINUX, which involved > adding a whopping -rdynamic to the build line, there were technologies missing from my

zdb -C shows an shift value on each vdev in my pool, I was just wondering if it is vdev specific, or pool wide. Google didn''t seem to know. I''m considering a mixed pool with some "advanced format" (4KB sector) drives, and some normal 512B sector drives, and was wondering if the ashift can be set per vdev, or only per pool. Theoretically, this would save me some size on

I four nodes setup to do active-backup bonding and the drivers loaded for the bonded network interfaces vary between tg3 and e100. All interfaces with the e100 driver loaded report errors much like what you see here: bonding: bond0: link status definitely down for interface eth2, disabling it e100: eth2: e100_watchdog: link up, 100Mbps, full-duplex bonding: bond0: link status definitely up for

> I'm having an issue getting a C6.6 install to work on a 3 TB dual hard >drive system, raid 0. I'm hoping that someone here can help. 1: Is this system booting UEFI or BIOS? 2: Is the disk partitioned with MBR or GPT? 3: Is /boot on its own partition? 3TB drives are larger than MBR and BIOS properly support, so they're only really expected to work on a system partitioned with

Greetings, Quick question: I am about to acquire some disks for use with ZFS (currently using zfs-fuse v0.7.0). I''m aware of some 4k alignment issues with Western Digital advanced format disks. As far as I can tell, the Hitachi Deskstar 7K3000 (HDS723030ALA640) uses 512B sectors and so I presume does not suffer from such issues (because it doesn''t lie about the physical layout

We have a 3TB external USB drive that I am trying to attach to some CentOS5 servers. I have tried an older Dell PE1950 and a newer R310 but neither one seems to be able to read the drive. It works no problem on windows servers/workstations and I was able to format with NTFS. I know there are different methods for formatting large disks but this one doesn't even seem to show up as a /dev/

CentOS 4.3 (fully updated, including CentOS Plus kernel). Running KDE 3.5.2 (fully updated from redhat.kde repo). I can't seem to get the OS to recognize my SD card when inserted into my USB card reader. Mepis 6 Beta 3 has no problem with it. DMESG sees nothing happening when the card is inserted. USB-STORAGE module is loaded.

How well suited is btrfs to low-end and high-end FLASH devices? Paraphrasing from a thread elsewhere: FLASH can be categorised into two classes, which have extremely different characteristics: (a) the low-end (USB, SDHC, CF, cheap ATA SSD); and (b) the high-end (SAS, PCIe, NAS, expensive ATA SSD). My own experience is that the low end (a) can have erase blocks as large as 4MBytes or more

Hi, my oi151 based home NAS is approaching a frightening "drive space" level. Right now the data volume is a 4*1TB Raid-Z1, 3 1/2" local disks individually connected to an 8 port LSI 6Gbit controller. So I can either exchange the disks one by one with autoexpand, use 2-4 TB disks and be happy. This was my original approach. However I am totally unclear about the 512b vs 4Kb issue.

Hi, I posted in the Solaris install forum as well about the fileserver I''m building for media files but wanted to ask more specific questions about zfs here. The setup is 8x500GB SATAII drives to start and down the road another 4x750 SATAII drives, the machine will mostly be doing reads and streaming data over GigaE. -I''m under the impression that ZFS+(ZFS2) is similar to

We just got in a few server-class drives. They're Seagate Constellations, 3TB. I went to partition and format, and did a mklabel gpt in parted. Ooops. It claims Sector size (logical/physical): 512B/512B After data sheet that doesn't tell me, and a long wait*, I spoke to a Seagate tech, who agreed that it *is* 4k physical. This is CentOS 6.2 Anyone know any way to correct this, or if

Hello all. What we have: SL6 - kernel 2.6.32-131.2.1.el6.x86_64 btrfs on mdadm RAID5 with 8 HDD - 27T partition. I see this at top: 1182 root 20 0 0 0 0 R 100.0 0.0 16:39.73 [btrfs-delalloc-] And LA is grow. What is this and how can I fix it? -- Best regards, Proskurin Kirill -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of

Hi. Is the problem with ZFS supporting 4k sectors or is the problem mixing 512 byte and 4k sector disks in one pool, or something else? I have seen alot of discussion on the 4k issue but I haven''t understood what the actual problem ZFS has with 4k sectors is. It''s getting harder and harder to find large disks with 512 byte sectors so what should we do? TIA...

I've been going along not noticing things happening right under my nose. so imagine my surprise when I discovered last night that my Centos 5 box has installed multiple new kernels over the last few months, as updates come out, and IT IS NOT BOOTING THE NEWST ONE. grub.conf says to boot kernel 0, and 0 is the newest one. but the one it actually boots is 6 or 8 down the list (clearly I've

I've managed to install CentOS 5.1 on S5000PAL with fakeraid Intel Embedded Raid Technology II Raid1 (LSI chipset) with some help of kickstart declaration 'driverdisk --source=http://.../driver.img' Then I've had some problems with yum update - new kernel didn't know about megasr.ko. I've solved it with commands: cd /lib/modules/ cp 2.6.18-53.el5PAE/updates/megasr.ko

OK todays problem. I have a HP N54L Microserver running centos 6.5. In this box I have a 3x2TB disk raid 5 array, which I am in the process of extending to a 4x2TB raid 5 array. I've added the new disk --> mdadm --add /dev/md0 /dev/sdb And grown the array --> mdadm --grow /dev/md0 --raid-devices=4 Now the problem the resync speed is v slow, it refuses to rise above 5MB, in general

----- Original Message ----- From: "Mark Milhollan" <mlm at pixelgate.net> To: "Jeff Boyce" <jboyce at meridianenv.com> Sent: Thursday, December 04, 2014 7:18 AM Subject: Re: [CentOS] CentOS 7 install software Raid on large drives error > On Wed, 3 Dec 2014, Jeff Boyce wrote: > >>I am trying to install CentOS 7 into a new Dell Precision 3610. I have

root at five-72 ~ # dd if=/dev/zero of=/dev/sdb bs=1M count=1000 1000+0 records in 1000+0 records out 1048576000 bytes (1.0 GB) copied, 8.67101 s, 121 MB/s root at five-72 ~ # parted /dev/sdb GNU Parted 2.1 Using /dev/sdb Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) mklabel gpt (parted) print Model: ATA ST3000DM001-1CH1 (scsi) -->