Software :: EXT3-fserror: Inode Bitmap For Group 4 Not In Group
May 25, 2011
I've been tasked with fixing a Red Hat system that dies with a kernel panic during the boot stage:
EXT3-fserror (dev sda1): ext3_check_descriptors: Inode bitmap for group 4 not in group (block 67239937)!
EXT3-fs: group descriptors corrupted!
mount: error mounting /dev/root on /sysroot as ext3: Invalid argument
I can boot into a Rescue CD, but I'm a bit out of my element because I don't use EXT3 myself, and I've never had to repair a corrupted file system before.
i have an external harddrive, hooked up by usb. /dev/sdb it came as a fat drive (sdb1). when i realized, i had copied 250 gb to it already. so, i made a new ext3 (sdb2) partition, copied the data from the fat to ext3, and then deleted the fat drive and moved the ext3 it with gparted. it mounted fine after it was moved, but after i tried to resize it, which didn't work, it will not mount.
I have a text file that currently has around 150 000 usernames in it. I need to somehow group them into smaller groups of 1000 and then add that value into the DB. for example user xzy group 1 (hopefully the groups will be digits incrementing)
how to search for 1000 then assign them group 1 and then 1001-1999 to group 2 etc.
i want secondary users can able to change the files permissions of primary group?user MAC is having www as a primary and httpd as secondary group. But he want to change the file permissions (chmod) httpd group files. Is it possible or not? I think its not possible. If it`s possible then let me know how?
I have a group (GROUP) with a number of users. I recently added a new user (NEW). NEW is able to read but not write group files, whereas all the other users in the group can read and write to the group files. The permissions for the group files indicate that all members of group should have write permission -rwxrwxr-x
/etc/group indicates that NEW is a member of GROUP ... GROUP:x:501:GROUP,OLD,OLD2,OLD3,OLD4,....,NEW
Don't know if it matters, but both OLD and NEW write to the GROUP files over an internet connection. why NEW can't write to GROUP files? Is there a maximum number of members in a group that I might have exceeded?
I have a number of users, categorised into various groups. I would like one of those groups ("developers") to be in the wheel group as well. I don't want to just copy the people from the developers group into wheel, because then when that group changes I'll have to change it in two places. Is there a way to specify that anyone in developers is in wheel, and have that be dynamic?
A bit of an oddity that I've recently run into with my storage folder in my system; it's a newly installed drive that I've set to mount at /storage. When I first tried to use it, programs that I used that attempted to write to it tossed Access Denied errors at me in their own way. Checking the permissions (at the Terminal, ls -l / | grep storage) showed that /storage was set to 'rwxrwxr--'--Owner and Group were given full read/write/execute, but Others could only read. However, my logon to my system is a member of group root. Why, then, with the above bits set, would I not be able to write to it? Changing Others permissions to rwx (and presumably rw would have worked out for me since I don't leave anything executable there) allowed me to write to it, but I don't understand why that would have been necessary. So far as I'm aware, the prior drive that was in my system--mounted at the same location--did not need this treatment.
Is it possible to allow a group/user to execute a command, where one of the parameters of the command is a group as well? example that does not work as intended:
Code: Cmnd_alias SU=/bin/su -l %group1 This example works sortof, it treats the "%group1" literally. I know I can list out the "/bin/su -l <eachuser>", but as you can imagine that is impractical. In this example, I want people in group2(not shown for brevity sake) to be able to su to someone in group1
I have been using CentOS 5. for around 3 months. It was all fine and was having a pleasant experience using CentOS. Today when i turned on my computer and booted CentOS i am having the below error: Grub comes up, allows me to select CentOS 5.4 kernel image. and displays RedHat Nash version: and then the below error occurs:
I am using Wind River Linux- 22.214.171.124-WR3.0bg_standard. The problem is whenever I execute "reboot, ls, cd" and many other commands the OS prompts me an error- "end request: i/o error, dev sda, sector "(different sector each time)" and EXT3-fs error (device sda1):ext3_get_inode_loc:unable to read inode block- inode-4088001, block-4097027 I also executed "dmesg", it also showed similar errors. Has the disk gone bad or the kernel is corrupted?
About a month and a half ago I purchased two new 500GB serial ATA hard drives from Best Buy to replace my other, very old 186GB SATA hard drive. Since then I've had issues with Linux. Sometimes when it's booting it gives a bunch of error messages, such as "failed to set xfermode," and then it boots. Other times, after INIT has started, I get ext3 errors about failing to read an inode block, then "cannot start /sbin/agetty" and "ID c5 respawning too fast," and at this point booting fails altogether. These errors seem to happen randomly. However, once the system has booted, everything seems to work fine, and there are no further issues.
I know it's not a faulty hard drive or filesystem because I've tried Linux on both hard drives numerous times, and I've reformatted many times, one time I even tried erasing one of the hard drives byte for byte and then formatting it, and still had issues.
I've tried Arch Linux, Gentoo, VectorLinux, and openSUSE, and all of them have given me these problems. The live CD's for Ubuntu 10.04, Clonezilla, and GParted all have trouble partitioning/cloning/installing to these hard drives. At this point, it's obvious to me that there is a universal problem with this particular model.
GRUB and Syslinux both work fine, and Windows XP works fine too. It's only Linux that's giving me issues.
I would rather not buy a new hard drive if I can help it, seeing as these two are almost brand new. Is there some BIOS setting that could be causing these problems? Is it some unsupported feature in the hard drives? Is it a bug in the Linux kernel?
The hard drive model is WD5000AADS. Both hard drives are this same model. My motherboard is an NForce 680i SLI.
EDIT: I've tried ext2/3, ReiserFS, and XFS, and all of them do this, so I don't think it's a filesystem issue.
We have a linux(SUSE 10) server that authenticates against AD(Windows 2003). Problem is anyone with an AD account can ssh in to the server. We don't want anyone to be able to login via ssh only the users in one particular group. I have tried editing the sshd_config file and adding the group to AllowGroups but this doesn't work. I have searched google and have not had much luck in finding anything.
What is the group 'users' (gid 100) for? It's tempting to use it as a general group for accounts that log in but would that cause a security risk? I've done a search for files owned by this group and there don't appear to be any. Googling the words gives very non-specific results!
I have four users in my red hat linux 9. I want that all these four users should add in a group i.e "Marketing". please guide me that using terminal which command may i write so that the users should added in the group.I does't want to use GUI interface to do it.