> > > > However, df reports that the root partition only has 60G on it. It > seems > > > > like fdisk is correctly querying the pdcraid module and communicating > with > > > > the card to discover the striped 120G virtual disk, while df seems to > be > > > > physically querying one of the physical drives in the array and > learning > > > > it's only 60G in size. > > > > > > That's weird - df shouldn't be querying drives at all, it should be > > > looking at filesystems. Have you installed and mounted a filesystem on > > > that huge root partition? > > > > To follow up my own response... > > > > I'll bet you had a filesystem on that drive before you put it into the > > array, right? > > > > Good thing there's nothing on it you want. Unmount it, replace it by > > running /sbin/mkfs on the array, and then mount it - you'll find that > > missing space you've been looking for. > > Sigh - actually my entire system that I've spent 3 days compiling from > Stage1 is on that array... > > I started out with nothing on any of the drives. The drives are 4 identical > drives I purchased and attached to the TX4 raid card immediately - they've > never known a life independent of the array. > > I took the virgin array, fdisked it into a 64M /root, 2G swap, and ~118G > root partition (I never use separate partitions for /home, /usr, etc, > because I can never size them correctly and wind up running out of space on > one while having plenty on another - it's annoying). fdisk had no trouble > with any of this and reports (even now) that it's a 118G partition mounted > on / > > I then merrily mkreiserfsed the partition and went about installing a > brand-new system. Actually, I never successfully got the mbr to work on the > array with Grub or Lilo, and wound up buying yet another drive simply to > boot from, which is another annoying story, but whatever. So my actual, > working /boot partition is on another (non-raid) drive. > > Only now, after finally getting everything installed, did I issue a df > command out of curiosity, just to see how much space my complete system > takes. It was then that I noticed it thinks I've only got 60G on the > partition, instead of the fdisked 120G. > > I'm not sure what to do. I suppose I could tar and copy the entire array > root partition over to the other, single drive (which is 160G), re-fdisk and > mkfs the array and copy everything back, but frankly, if df is simply wrong > and I really do have 120G available on the partition I'd rather not do > that... > > Eric >
Default behaivor of 'df' is to output the number of blocks on the hard disk. If your block size is set to 2kb, then it may appear as though you have half the capacity that you really do. Try 'df -h'. the '-h' flag is for "human-readable" output. Hope that helps. -- [EMAIL PROTECTED] mailing list
