姜路
2014-Mar-18 09:43 UTC
[Gluster-users] gluster3.3.0 cause the ext4 system error then the linux(2.6.32-220.el6.x86_64) kernel panic...
jianglulu hello everyone,when i write the data in the server which used 2.6.32-220.el6.x86_64 kernel and gluster3.3.0 ,the server occur "ext4_mb_complex_scan_group: 27 free blocks as per group info. But bitmap says 0 " error and then kernel panic,so i want to ask some suggests for this: 1.is my disk has some problemes? 2.is the ext4 filesystem has some errors? 3.should i Upgrade system for linux or gluster? these are just some of the errors: EXT4-fs error (device sdf1): ext4_lookup: deleted inode referenced: 13787177 EXT4-fs (sdb1): ext4_check_descriptors: Block bitmap for group 5760 not in group (block 0)! EXT4-fs (sdb1): group descriptors corrupted! EXT4-fs (sdb1): ext4_check_descriptors: Block bitmap for group 5760 not in group (block 0)! EXT4-fs (sdb1): group descriptors corrupted! sorry for my poor EN~~ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20140318/1ad581a3/attachment.html>
Carlos Capriotti
2014-Mar-18 13:07 UTC
[Gluster-users] gluster3.3.0 cause the ext4 system error then the linux(2.6.32-220.el6.x86_64) kernel panic...
Ok...>From previous posts, there still seems to be a kernel but, unaddressed bydevelopers, which affects how ext4 works, and indeed makes its use with gluster unreliable. Specially on older versions of GLuster. Upgrading to 3.4.2 would be nice, if you can. If at all possible, use xfs instead of ext4. This is an official recommendation. prepare you filesystem with: mkfs.xfs -i size=512 /dev/yourdevicehere or any variation, BUT, keeping the inode size value at 512. Not quite sure what you mean by "my disks have problems"; You might mean the physical disk, the volume on your RAID (if any), your LVM volume, your gluster volume... BUT, before moving to that arena, you might want to do the steps above. If your system is a test system, upgrade to 3.4.2, and start using XFS. If it is a production system, you will have to find a way to do the transition. KR, Carlos On Tue, Mar 18, 2014 at 10:43 AM, ?? <jll19851108 at 163.com> wrote:> jianglulu > hello everyone,when i write the data in the server which used > 2.6.32-220.el6.x86_64 kernel and gluster3.3.0 ,the server occur > "ext4_mb_complex_scan_group: 27 free blocks as per group info. But bitmap > says 0 " error and then kernel panic,so i want to ask some suggests for > this: > > 1.is my disk has some problemes? > 2.is the ext4 filesystem has some errors? > 3.should i Upgrade system for linux or gluster? > > these are just some of the errors: > EXT4-fs error (device sdf1): ext4_lookup: deleted inode referenced: > 13787177 > EXT4-fs (sdb1): ext4_check_descriptors: Block bitmap for group 5760 not > in group (block 0)! > EXT4-fs (sdb1): group descriptors corrupted! > EXT4-fs (sdb1): ext4_check_descriptors: Block bitmap for group 5760 not in > group (block 0)! > EXT4-fs (sdb1): group descriptors corrupted! > > > sorry for my poor EN~~ > > > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://supercolony.gluster.org/mailman/listinfo/gluster-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20140318/dc9dc6e8/attachment.html>