Neil Zanella (nzanella@cs.mun.ca)
Fri, 29 Jan 1999 15:33:03 -0330 (NST)
There is something I am missing:
If /dev/sda is the floppy in my Zip drive then what is the advantage
to naming it /dev/sda4 as opposed to /dev/sda? After all, as
far as I understand it brand new disks have partitions /dev/sda1,
/dev/sda2, and /dev/sda3 with zero sizes, right?
On Fri, 29 Jan 1999, David Campbell wrote:
> You either partition /dev/sda (and create the /dev/sda4 partition),
> run mkext2fs on /dev/sda4 and then mount it.
>
> OR
>
> Run mkex2fs on /dev/sda and then mount /dev/sda (not /dev/sda4).
I think "mke2fs /dev/sda4" followed by "mount -t ext2 /dev/sda4 /mnt/zip"
does what I want. After all I have no scsi devices other than my parallel
port Zip250 drive. Here is the result of my commands on a 250MB Zip disk:
[[root@river /root]# mke2fs /dev/sda4
mke2fs 1.10, 24-Apr-97 for EXT2 FS 0.5b, 95/08/09
Linux ext2 filesystem format
Filesystem label=
61200 inodes, 244720 blocks
12236 blocks (5.00%) reserved for the super user
First data block=1
Block size=1024 (log=0)
Fragment size=1024 (log=0)
30 block groups
8192 blocks per group, 8192 fragments per group
2040 inodes per group
Superblock backups stored on blocks:
8193, 16385, 24577, 32769, 40961, 49153, 57345, 65537, 73729,
81921, 90113, 98305, 106497, 114689, 122881, 131073, 139265,
147457,
155649, 163841, 172033, 180225, 188417, 196609, 204801, 212993,
221185,
229377, 237569
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
[[root@river /root]# mount -t ext2 /dev/sda4 /mnt/zip
[[root@river /root]# ls /mnt/zip
lost+found
[[root@river /root]# df
Filesystem 1024-blocks Used Available Capacity Mounted on
/dev/hda5 62431 43866 15341 74% /
/dev/hda7 103413 8813 89260 9% /home
/dev/hda6 766744 677824 49308 93% /usr
/dev/hda1 1030128 586648 443480 57% /dos
/dev/sda4 236949 13 224700 0% /mnt/zip
[[root@river /root]#
Here is a similar setup for the 100MB Zip disk.
This time, instead of formatting my disk as /dev/sda4 I format it as
/dev/sda :
[[root@river /root]# umount /mnt/zip
[[root@river /root]# mke2fs /dev/sda4
mke2fs 1.10, 24-Apr-97 for EXT2 FS 0.5b, 95/08/09
mke2fs: Device not configured while trying to determine filesystem size
[[root@river /root]# mount -t ext2 /mnt/zip
usage: mount [-hV]
mount -a [-nfFrvw] [-t vfstypes]
mount [-nfrvw] [-o options] special | node
mount [-nfrvw] [-t vfstype] [-o options] special node
[[root@river /root]# mount -t ext2 /dev/sda4 /mnt/zip
mount: /dev/sda4 is not a valid block device
[[root@river /root]# mke2fs /dev/sda
mke2fs 1.10, 24-Apr-97 for EXT2 FS 0.5b, 95/08/09
/dev/sda is entire device, not just one partition!
Proceed anyway? (y,n) y
Linux ext2 filesystem format
Filesystem label=
24576 inodes, 98304 blocks
4915 blocks (5.00%) reserved for the super user
First data block=1
Block size=1024 (log=0)
Fragment size=1024 (log=0)
12 block groups
8192 blocks per group, 8192 fragments per group
2048 inodes per group
Superblock backups stored on blocks:
8193, 16385, 24577, 32769, 40961, 49153, 57345, 65537, 73729,
81921, 90113
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
[[root@river /root]# mount -t ext2 /dev/sda /mnt/zip
[[root@river /root]# ls /mnt/zip
lost+found
Thanks for your help,
Best Regards,
Neil Zanella
nzanella@ganymede.cs.mun.ca
-- To unsubscribe, send mail to: linux-parport-request@torque.net --
-- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2.0b3 on Fri 29 Jan 1999 - 14:01:46 EST