resize2fs: Bad magic number in super-block while t

resize2fs: Bad magic number in super-block while trying to open /dev/mapper/cl-root

[[email protected] ~]# df -Th

Filesystem          Type      Size  Used      Avail   Use%   Mounted on

/dev/mapper/cl-root      xfs     18G     18G    897M    96%    /

devtmpfs            devtmpfs  901M     0      901M   0%     /dev

tmpfs              tmpfs     912M     0     912M   0%     /dev/shm

tmpfs              tmpfs     912M    608K    912M   1%    /run

tmpfs              tmpfs     912M     0     912M   0%     /sys/fs/cgroup

/dev/sda1           xfs      1014M    186M    829M  19%     /boot

tmpfs              tmpfs     183M     0     183M   0%     /run/user/0

[[email protected] ~]# vgdisplay

--- Volume group ---

VG Name               cl

System ID

Format                lvm2

Metadata Areas        1

Metadata Sequence No  3

VG Access             read/write

VG Status             resizable

MAX LV                0

Cur LV                2

Open LV               2

Max PV                0

Cur PV                1

Act PV                1

VG Size               <19.00 GiB

PE Size               4.00 MiB

Total PE              4863

Alloc PE / Size       4862 / 18.99 GiB

Free  PE / Size       1 / 4.00 MiB

VG UUID               0g6KUL-2kdC-e4Ml-EMFH-2JYs-SNUT-bn09Od

[[email protected] ~]# pvcreate /dev/sdc

Physical volume "/dev/sdc" successfully created.

[[email protected] ~]# vgextend c1 /dev/sdc

Volume group "c1" not found

Cannot process volume group c1

[[email protected] ~]# vgscan

Reading volume groups from cache.

Found volume group "cl" using metadata type lvm2

[[email protected] ~]# vgextend lvm2 /dev/sdc

Volume group "lvm2" not found

Cannot process volume group lvm2

[[email protected] ~]# pscan

-bash: pscan: command not found

[[email protected] ~]# pvscan

PV /dev/sda2   VG cl              lvm2 [<19.00 GiB / 4.00 MiB free]

PV /dev/sdc                       lvm2 [20.00 GiB]

Total: 2 [<39.00 GiB] / in use: 1 [<19.00 GiB] / in no VG: 1 [20.00 GiB]

[[email protected] ~]# pvscan

PV /dev/sda2   VG cl              lvm2 [<19.00 GiB / 4.00 MiB free]

PV /dev/sdc                       lvm2 [20.00 GiB]

Total: 2 [<39.00 GiB] / in use: 1 [<19.00 GiB] / in no VG: 1 [20.00 GiB]

[[email protected] ~]# vgextend cl /dev/sdc

Volume group "cl" successfully extended

[[email protected] ~]# vgdisplay

--- Volume group ---

VG Name               cl

System ID

Format                lvm2

Metadata Areas        2

Metadata Sequence No  4

VG Access             read/write

VG Status             resizable

MAX LV                0

Cur LV                2

Open LV               2

Max PV                0

Cur PV                2

Act PV                2

VG Size               38.99 GiB

PE Size               4.00 MiB

Total PE              9982

Alloc PE / Size       4862 / 18.99 GiB

Free  PE / Size       5120 / 20.00 GiB

VG UUID               0g6KUL-2kdC-e4Ml-EMFH-2JYs-SNUT-bn09Od

[[email protected] ~]# resize2fs /dev/mapper/cl-root

resize2fs 1.42.9 (28-Dec-2013)

resize2fs: Bad magic number in super-block while trying to open /dev/mapper/cl-root

Couldn't find valid filesystem superblock.

原文地址:http://blog.51cto.com/sf1314/2062106

时间: 2024-10-10 06:13:07

resize2fs: Bad magic number in super-block while t的相关文章

LVM XFS增加硬盘分区容量(resize2fs: Bad magic number in super-block while)

LVM XFS增加硬盘分区容量(resize2fs: Bad magic number in super-block while) 2015-09-04 11:28:01 分类: Linux LVM XFS增加硬盘分区容量(resize2fs: Bad magic number in super-block while) 给某个硬盘增加分区之后 [[email protected]-213-66 ~]# df -h Filesystem Size Used Avail Use% Mounted

LVM 扩容报错:resize2fs: Bad magic number in super-block while......

废话不多说,这里直接举例说明: [[email protected] ~]# df -hFilesystem Size Used Avail Use% Mounted on/dev/mapper/vg_mysql0121366-LogVol02 7.7G 2.6G 4.8G 36% /tmpfs 495M 0 495M 0% /dev/shm/dev/sda1 194M 29M 155M 16% /boot/dev/mapper/vg_mysql0121366-LogVol01 8.0G 3.1

resize2fs: Bad magic number in super-block while trying to open

I am trying to resize a logical volume on CentOS7 but am running into the following error: resize2fs 1.42.9 (28-Dec-2013) resize2fs: Bad magic number in super-block while trying to open /dev/mapper/centos-root Couldn't find valid filesystem superbloc

LVM做扩容Bad magic number in super-block while trying

环境:CentOS Linux release 7.2.1511 (Core)做LVM 逻辑卷扩容的时候报错: (扩容逻辑边界)shell>resize2fs -p /dev/mapper/centos-root resize2fs 1.42.9 (28-Dec-2013)resize2fs: Bad magic number in super-block while trying to open /dev/mapper/centos-rootCouldn't find valid filesy

btrfs super block

1 /* 2 * the super block basically lists the main trees of the FS 3 * it currently lacks any block count etc etc 4 */ 5 struct btrfs_super_block { 6 u8 csum[BTRFS_CSUM_SIZE]; 7 /* the first 4 fields must match struct btrfs_header */ 8 u8 fsid[BTRFS_F

故障处理:磁盘扩容出错:e2fsck: Bad magic number in super-block while trying to open /dev/vdb1

按照阿里云官网教程对云服务器进行磁盘扩容,使用fdisk重新分区,最后使用e2fsck和resize2fs来完成文件系统层面的扩容 在执行"e2fsck -f /dev/vdb1"命令时报错,如果你的问题和下面的错误一样,可以接着往下看: [[email protected]aliyunsrv ~]# e2fsck -f /dev/vdb1 e2fsck 1.41.12 (17-May-2010) e2fsck: Superblock invalid, trying backup bl

magic number介绍

magic number:魔数,这是放在linux的目录中的文件信息块中的一个标识符,一般只有几位,用来标识该文件是什么类型的文件,可以被什么样的应用使用.这个魔数不是固定的,有时候一个文件信息中的魔数可能会不断变化.这个东西不重要的,对用户造不成多少影响.两个例子:1.ELF文件的头部,前4个字节是魔数.这个常用于识别文件类型等.linux上,二进制的可执行文件的前四个字节是7f45,而在AIX上,二进制可执行文件的前四个字节是0x01df.2.内核程序中,给一些 IO 操作进行编号时,也会用

ZOJ 3622 Magic Number(数)

题意  假设一个正整数y满足  将随意正整数x放到y的左边得到的数z满足 z%y==0  那么这个数就是个Magic Number   给你一个范围  求这个范围内Magic Number的个数 令 l表示y的位数  ly=10^l  那么z=x*ly + y  要z%y==0   easy看出  仅仅需 x*ly%y==0 又由于x是随意的  所以一个Magic Number必须满足 ly%y==0 y<2^31  所以l最大为10 直接枚举l  找到全部符合的y即可了 当 ly%y==0  

Magic Number(Levenshtein distance算法)

Magic Number Time Limit:1000MS     Memory Limit:65536KB     64bit IO Format:%I64d & %I64u Submit Status Practice HDU 4323 Description There are many magic numbers whose lengths are less than 10. Given some queries, each contains a single number, if t