search for: groups_count

...e the cause... here are the lines of the last crashes (can't resolve call trace because the old kernels are gone and i didn't resolve the traces when they occured) --- Dec 9 19:55:30 srck@trottelkunde Kernel panic: EXT3-fs panic (device ide1(22,66)): load_block_bitmap: block_group >= groups_count - block_group = 131071, groups_count = 94 Dec 9 19:55:30 srck@trottelkunde Assertion failure in journal_start() at transaction.c:227: "handle->h_transaction->t_journal == journal" --- Jan 4 11:29:42 srck@trottelkunde Kernel panic: EXT3-fs panic (device ide1(22,67)): load_block_b...

Hi, When trying to run a particular program, I reproducibly get a few dozen kernel messages of the form: attempt to access beyond end of device 03:06: rw=0, want=536995844, limit=11680168 attempt to access beyond end of device 03:06: rw=0, want=1342296068, limit=11680168

Hi! I experienced an ext3 crash a few days ago, the corresponding part of my kernel log is attached (there were no IDE-errors, just the ext3 stuff). The /home partition (/dev/hdd2) got remounted ro, so the box was still usable somehow (was able to log in, kill stuff and reboot it). I rebooted it, it came back up again w/o any problems, remounted /home ro and did a e2fsck on it, which reported

...* +ufs_get_inode(struct fs_info *fs, int inr) +{ + const char *data; + uint32_t group, inode_offset, inode_table; + uint32_t block_num, block_off; + + /* Get cylinder group nr. */ + group = inr / UFS_SB(fs)->inodes_per_cg; + /* + * Ensuring group will not exceed the range 0:groups_count-1. + * By the way, this should *never* happen. + * Unless the (on-disk) fs structure is corrupted! + */ + if (group >= UFS_SB(fs)->groups_count) { + printf("ufs_get_inode: " + "group(%d) exceeded the avail. range (0:%d)\n", + group, UFS_SB(fs)->groups_c...

...* +ufs_get_inode(struct fs_info *fs, int inr) +{ + const char *data; + uint32_t group, inode_offset, inode_table; + uint32_t block_num, block_off; + + /* Get cylinder group nr. */ + group = inr / UFS_SB(fs)->inodes_per_cg; + /* + * Ensuring group will not exceed the range 0:groups_count-1. + * By the way, this should *never* happen. + * Unless the (on-disk) fs structure is corrupted! + */ + if (group >= UFS_SB(fs)->groups_count) { + printf("ufs_get_inode: " + "group(%d) exceeded the avail. range (0:%d)\n", + group, UFS_SB(fs)->groups_c...

...*fs, uint32_t group_num) +static const void *__ext2_get_group_desc(struct fs_info *fs, uint32_t group_num) { struct ext2_sb_info *sbi = EXT2_SB(fs); uint32_t desc_block, desc_index; - const struct ext2_group_desc *desc_data_block; + uint8_t *p; if (group_num >= sbi->s_groups_count) { printf ("ext2_get_group_desc" "block_group >= groups_count - " "block_group = %d, groups_count = %d", group_num, sbi->s_groups_count); - return NULL; } @@ -49,8 +44,17 @@ ext2_get_group_desc(struct fs_info *fs, uint32_t group_num) de...

...device ide0(3,5)): ext3_free_blocks: Freeing blocks not in datazone - block = 3251122320, count = 1 EXT3-fs error (device ide0(3,5)): ext3_free_blocks: Freeing blocks not in datazone - block = 3251122320, count = 1 Kernel panic: EXT3-fs panic (device ide0(3,5)): load_block_bitmap: block_group >= groups_count - block_group = 131071, groups_count = 47 EXT3-fs error (device ide0(3,5)): ext3_free_blocks: Freeing block in system zone - block = 2 Can someone push me in a direction please? Pascal

From: Raphael S. Carvalho <raphael.scarv at gmail.com> Wrote the documentation below. I think it would be good to push the doc to the wiki as soon as the UFS support gets merged. Unix Fast File System (UFS/FFS) 1/2 on Syslinux - (usage/install) ----- There is a confusion about the name of this file system, then I decided to contact the author who replied: "The name has always been

From: Raphael S. Carvalho <raphael.scarv at gmail.com> Change since v1: * Fix bug on dentry structure (thank you specification; btw, sarcasm), and consequently a bug on ufs_readdir. * Add readlink support (applied tests for symlinks whose destionation path were stored in blk pointers and the file itself). * Several improvements. Wrote the documentation below. I think it would be good to