我使用mdadm从我的一个磁盘得到了一个相当奇怪的结果。 它被设置为raid 10中的2TB磁盘中的4个。
# df Filesystem Size Used Avail Use% Mounted on /dev/md2 3.6T 40G 3.4T 2% / <------ this one tmpfs 7.8G 0 7.8G 0% /dev/shm /dev/md0 4.9G 189M 4.4G 5% /boot
实际的磁盘使用量大致在2TB左右。 但是,它只报告40GB的使用量。
我在/ var / log / messages和/ var / log / dmesg(同样的)中看到类似这样的错误。
Feb 13 05:46:00 las kernel: EXT4-fs error (device md2): ext4_mb_generate_buddy: EXT4-fs: group 24449: 0 blocks in bitmap, 32768 in gd Feb 13 05:46:00 las kernel: EXT4-fs error (device md2): ext4_mb_generate_buddy: EXT4-fs: group 24450: 3 blocks in bitmap, 32771 in gd Feb 13 05:46:00 las kernel: EXT4-fs error (device md2): ext4_mb_generate_buddy: EXT4-fs: group 24451: 6 blocks in bitmap, 32766 in gd Feb 13 05:46:00 las kernel: EXT4-fs error (device md2): ext4_mb_generate_buddy: EXT4-fs: group 24452: 50 blocks in bitmap, 32742 in gd Feb 13 05:46:00 las kernel: EXT4-fs error (device md2): ext4_mb_generate_buddy: EXT4-fs: group 24453: 43 blocks in bitmap, 32768 in gd Feb 13 05:46:00 las kernel: EXT4-fs error (device md2): ext4_mb_generate_buddy: EXT4-fs: group 24454: 30 blocks in bitmap, 32768 in gd Feb 13 05:46:00 las kernel: EXT4-fs error (device md2): ext4_mb_generate_buddy: EXT4-fs: group 24455: 77 blocks in bitmap, 32768 in gd Feb 13 05:46:00 las kernel: EXT4-fs error (device md2): ext4_mb_generate_buddy: EXT4-fs: group 24456: 27 blocks in bitmap, 32744 in gd Feb 13 05:46:00 las kernel: EXT4-fs error (device md2): ext4_mb_generate_buddy: EXT4-fs: group 24457: 68 blocks in bitmap, 32265 in gd Feb 13 05:46:00 las kernel: EXT4-fs error (device md2): ext4_mb_generate_buddy: EXT4-fs: group 24458: 32 blocks in bitmap, 1804 in gd Feb 13 05:46:00 las kernel: JBD: Spotted dirty metadata buffer (dev = md2, blocknr = 0). There's a risk of filesystem corruption in case of system crash. Feb 13 05:46:00 las kernel: JBD: Spotted dirty metadata buffer (dev = md2, blocknr = 0). There's a risk of filesystem corruption in case of system crash. Feb 13 05:46:00 las kernel: JBD: Spotted dirty metadata buffer (dev = md2, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
但不确定要做什么。
mdadm详细显示…
# mdadm --detail /dev/md2 /dev/md2: Version : 1.1 Creation Time : Thu Oct 18 22:20:38 2012 Raid Level : raid10 Array Size : 3896783872 (3716.26 GiB 3990.31 GB) Used Dev Size : 1948391936 (1858.13 GiB 1995.15 GB) Raid Devices : 4 Total Devices : 4 Persistence : Superblock is persistent Intent Bitmap : Internal Update Time : Wed Feb 13 05:58:12 2013 State : active Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Layout : near=2 Chunk Size : 512K Name : i2274.userdns.net:2 UUID : f64e69c7:8342cdd1:0a275bbf:3ba052f4 Events : 275873 Number Major Minor RaidDevice State 0 8 2 0 active sync /dev/sda2 1 8 18 1 active sync /dev/sdb2 2 8 33 2 active sync /dev/sdc1 3 8 49 3 active sync /dev/sdd1
最后,我只是通过echo y > /forcefsck运行fsck并reboot ,但似乎没有任何改变。 我认为磁盘损坏,但不知如何进行。
只是为了解决这个问题,我做了一个完整的fsck,就像@kormocbuild议的那样,在非交互模式下启动。 这已经解决了这个问题。