Hi, On Fri, 2011-11-11 at 17:04 +0800, Sherlock Zhang wrote: > Hi Bob > Thank you for your advice, > I had dump the FS head. > #dd if=/dev/sdc of=/home/disk.dump bs=4096 count=1000 > #file disk.dump > disk.dump: Linux GFS2 Filesystem (blocksize 4096, lockproto > fsck_nolock) > and I also try > # gfs2_tool sb /dev/sdc all > mh_magic = 0x01161970 > mh_type = 1 > mh_format = 100 > sb_fs_format = 1801 > sb_multihost_format = 1900 > sb_bsize = 4096 > sb_bsize_shift = 12 > no_formal_ino = 2 > no_addr = 35 > no_formal_ino = 1 > no_addr = 34 > sb_lockproto = fsck_nolock > sb_locktable = > uuid = 5a8234ba-ad89-f87a-c98b-807e307085fe > > > then try to mount the storage > #mount.gfs2 -o lockproto=fsck_nolock /dev/sdc /opt > error mounting /dev/sdc on /opt: No such file or directory > > > #dmesg > GFS2: can't find protocol fsck_nolock > > > Is this mean the filesystem structure still ok? > why should dmesg will report can't find fsck_nolock protocol? > Did I miss something? > > > Thank you > This means that fsck has stopped before it finished for some reason. It replaces the lock protocol with fsck_nolock while it is running so that if this happens you cannot remount the filesystem which is potentially damaged. If fsck is not completing correctly then we need to look into why that is, Steve. > On Thu, Nov 10, 2011 at 10:45 PM, Bob Peterson <rpeterso@xxxxxxxxxx> > wrote: > ----- Original Message ----- > | Hi > | The host use UIT's CT1600 and UIT's 2000E IP-SAN storage > (single > | LUN > | 10TB) > | last time the switch got a power failure during the data > backup (the > | iSCSI > | connection is lost) > | after the iSCSI reconneted, the filesystem was unable to > use. > | > | So I try use fsck.gfs2 to fix the filesystem problem.but > there is a > | error > | message and I got no idea with this error. > | > | [root@Toureg ~]# fsck.gfs2 /dev/sdc > | Initializing fsck > | The system master directory seems to be destroyed. > | Okay to rebuild it? (y/n)y > | Trying to rebuild the master directory. > | libgfs2.h: out of space > > > Hi, > > The only time I've seen this error before is when the device > was badly damaged. I don't know how that one was damaged, but > it looked like the RAID controller had completely rearranged > the blocks on the media. > > If you are a Red Hat customer, please call the Red Hat support > number and ask for help. > > A number of things can cause this message: > 1. Scrambled blocks on media > 2. A disk failed > 3. Running fsck on the wrong device. For example, if /dev/sdc > is partitioned (should have specified /dev/sdc1?) or if > /dev/sdc is supposed to be part of an LVM2 logical volume, > (should you have specified /dev/volgrp/logvol (for example) > rather than /dev/sdc? > > Either way, something's seriously wrong with it. If it were my > device, I'd dump the first few MB to a file and see what's > there, > compared to what should be there. > > Regards, > > Bob Peterson > Red Hat File Systems > > -- > Linux-cluster mailing list > Linux-cluster@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/linux-cluster > > > > > -- > Thank you > > Best regards > ************************************************************************************************* > Sherlock Zhang 张 国荣 > Technical Supporter East China Technical Support Department > > Address: Room 23E No. 728 West Yanan Road Changning DC. Shanghai China > Post code: 20050 > > Office: +86 021 62253300 ext. 803 > Mobile: +86 133 8600 6305 > www.uit.com.cn > > > ************************************************************************************************* > > -- > Linux-cluster mailing list > Linux-cluster@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/linux-cluster -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
