On Monday 2009 January 05 12:46:03 Dov Oxenberg wrote: > The Server has five 72GB > hot swap SCSI disks and I configured two arrays - one > logical disk 72GB RAID1 to house the O/S and the remaining 200GB array as a > second logical disk which I intend to use as storage for FTP > upload/download. RAID-0? I assume this is only temporary storage then, yes? If one drive fails in a RAID-0, the entire array is toast. > What I need help with is > in using the available space on the second logical disk. I suspect I fudged > the partitioning - I THOUGHT I partitioned the 200GB drive as EXT3 and the > space was available for use, but here is what is happening. What tool did you use? There's no partition type specifically for ext3, AFAIK. Even if there was, you'd still need to create the filesystem. To do that from the command-line something like "mkfs.ext3 /dev/cciss/c0d1p1" would be required. > I created a > directory under /home named "secureftp." I also added this entry to my > FSTAB, contents of which look like this: > SERVERNAME:/# cat /etc/fstab# > /etc/fstab: static file system information.## <file system> <mount point> > <type> <options> <dump> <pass>proc /proc proc > defaults 0 0/dev/cciss/c0d0p1 / ext3 > defaults,errors=remount-ro 0 1/dev/cciss/c0d0p5 none swap > sw 0 0/dev/hda /media/cdrom0 udf,iso9660 > user,noauto 0 0/dev/fd0 /media/floppy0 auto > rw,user,noauto 0 0/dev/cciss/c0d1p1 /securedata ext3 defaults > 0 0 I assume it's not missing all the newlines and your mailer just screwed that up? If not, that might be part of your problem. Also, your prose above indicates you wanted it mounted at /home/secureftp, but your fstab entry says you want it at /securedata. Make sure you are consistent. > I run > the command "mount -t ext3 /dev/cciss/c0d1p1 /securedata" the system > responds with "mount: wrong fs type, bad option..." Basically, that means that it can't find the filesystem you've specified. > SERVERNAME:/# dmesg | tail heads= 255, sectors= 32, > cylinders= 52299 cciss/c0d1: p1 < > blocks= 426759840 block_size= 512 > heads= 255, sectors= 32, cylinders= 52299 cciss/c0d1: p1 < >attempt to > access beyond end of devicecciss/c0d1p1: rw=0, want=4, limit=2EXT3-fs: > unable to read superblock Attempt to access beyond the end of device is a bit unusual. I suppose that might simply have been the ext3 driver looking for one of the extra recovery superblocks. For now, I'll ignore it and focus on "unable to read superblock" which means the filesystem is either corrupt or hasn't been created yest. > I thought the "superblock" was the 5% of space reserved by the system so I > can perform root maintenance should the disk become full, the data corrupt, > etc. No, the superblock is the area of the filesystem (usually stored toward the beginning of the drive) that contains information about the filesystem as a whole. For example, it generally stores what size the filesystem thinks it is, what block size is in use (if the fs supports multiple block sizes), any options or sub-options that are expected to be persistent, maybe a free space list or bitmap, etc. It also stores things like UUID and LABEL. Most, if not all, filesystems have one. The reserved space and inodes are fairly ext[234] specific -- most other filesystems will let you shoot yourself in the foot quite easily. Also, even on ext[234] that percentage is adjustable and can be eliminated entirely if need be. UNIX and Linux systems traditionally behave very poorly, if at all, when no filesystem can be written to -- a lot of programs/scripts require at least some scratch space. This reservation by ext[234] can make it quite a bit easier to recover from that state. -- Boyd Stephen Smith Jr. ,= ,-_-. =. bss@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/
Attachment:
signature.asc
Description: This is a digitally signed message part.