1.使用fdisk成功建立主分區/dev/sdb1,查看/proc/partitions中的分區信息 node
[root@localhost ~]# cat /proc/partitions major minor #blocks name 8 0 20971520 sda 8 1 512000 sda1 8 2 20458496 sda2 8 16 10485760 sdb 8 17 522081 sdb1 8 32 10485760 sdc 8 33 1060258 sdc1 8 34 1060290 sdc2 8 35 1060290 sdc3 8 36 1 sdc4 8 37 1060258 sdc5 253 0 18849792 dm-0 253 1 1605632 dm-1 253 2 1060258 dm-2 253 3 1060290 dm-3 253 4 1060290 dm-4 253 5 1 dm-5 253 6 1060258 dm-6 253 7 112423 dm-7 253 8 1 dm-8 253 9 522081 dm-9
2.使用mke2fs建立文件系統提示/dev/sdb1正在被系統使用app
[root@localhost ~]# mke2fs -t ext4 /dev/sdb1 mke2fs 1.41.12 (17-May-2010) /dev/sdb1 is apparently in use by the system; will not make a filesystem here!
3.使用mount查看/dev/sdb1是否被掛載,發現/dev/sdb1並無被掛載 ide
[root@localhost ~]# mount /dev/mapper/VolGroup-lv_root on / type ext4 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw,rootcontext="system_u:object_r:tmpfs_t:s0") /dev/sda1 on /boot type ext4 (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
4.使用dd命令發現磁盤讀寫正常spa
[root@localhost ~]# fdisk -l /dev/sdb Disk /dev/sdb: 10.7 GB, 10737418240 bytes 255 heads, 63 sectors/track, 1305 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x1c69f2ed Device Boot Start End Blocks Id System /dev/sdb1 1 65 522081 83 Linux [root@localhost ~]# dd if=/dev/zero of=/dev/sdb bs=512 count=1 1+0 records in 1+0 records out 512 bytes (512 B) copied, 0.000116963 s, 4.4 MB/s [root@localhost ~]# fdisk -l /dev/sdb Disk /dev/sdb: 10.7 GB, 10737418240 bytes 255 heads, 63 sectors/track, 1305 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000
5.使用fuser查看/dev/sdb1磁盤被系統中那個進程使用,發現並沒用進程使用該磁盤 orm
[root@localhost ~]# fuser /dev/sdb1 [root@localhost ~]#
6.使用dmsetup status命令發現 /dev/sd1 正在被dm服務佔用,因此咱們建立文件系統時提示報錯。咱們手工的移除,就能夠正常的建立文件系統進程
[root@localhost ~]# dmsetup status VolGroup-lv_swap: 0 3211264 linear VolGroup-lv_root: 0 37699584 linear sdb2: 0 2 linear sdb1: 0 224847 linear sdc5: 0 2120517 linear sdc4: 0 2 linear sdc3: 0 2120580 linear sdc2: 0 2120580 linear sdc1: 0 2120517 linear sdb5: 0 1044162 linear
7.手工的移除/dev/sdb的映射關係(取消佔用),就能夠正常的建立文件系統ip
[root@localhost ~]# dmsetup remove sdb1 [root@localhost ~]# dmsetup remove sdb2 [root@localhost ~]# dmsetup remove sdb5 [root@localhost ~]# dmsetup status VolGroup-lv_swap: 0 3211264 linear VolGroup-lv_root: 0 37699584 linear sdc5: 0 2120517 linear sdc4: 0 2 linear sdc3: 0 2120580 linear sdc2: 0 2120580 linear sdc1: 0 2120517 linear
8.成功建立文件系統且類型爲ext4rem
[root@localhost ~]# mke2fs -t ext4 /dev/sdb1 mke2fs 1.41.12 (17-May-2010) Filesystem label= OS type: Linux Block size=1024 (log=0) Fragment size=1024 (log=0) Stride=0 blocks, Stripe width=0 blocks 130560 inodes, 522080 blocks 26104 blocks (5.00%) reserved for the super user First data block=1 Maximum filesystem blocks=67633152 64 block groups 8192 blocks per group, 8192 fragments per group 2040 inodes per group Superblock backups stored on blocks: 8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409 Writing inode tables: done Creating journal (8192 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 24 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. [root@localhost ~]#
[root@localhost ~]# blkid /dev/sdb1 /dev/sdb1: UUID="7fe362b4-389b-40f8-91ed-07572abc350a" TYPE="ext4"