search for: init_special_inode

...ated but I believe I am running a kernel that contains these fixes. My kernel is 2.6.18-194.32.1.el5 on one of the most effected hosts. Does anyone else have experience with similar issues or know of the status of this Bug/KB? I can install, boot, run, and then at some seemingly random moment - init_special_inode: bogus i_mode (50632) init_special_inode: bogus i_mode (137147) init_special_inode: bogus i_mode (172036) init_special_inode: bogus i_mode (175720) init_special_inode: bogus i_mode (72350) init_special_inode: bogus i_mode (174751) EXT3-fs error (device sdb2): ext3_lookup: unlinked inode 19698169 in...

...ew mount of the partition and copy data on the partition you get the errors again. Also with Kernel 2.6.17.3 I got this problems. A raid volume check with the areca command line tools doesn't find any errors. Errors from dmesg / kernel.log: EXT3-fs: mounted filesystem with ordered data mode. init_special_inode: bogus i_mode (113301) init_special_inode: bogus i_mode (170101) init_special_inode: bogus i_mode (115140) init_special_inode: bogus i_mode (117302) init_special_inode: bogus i_mode (111700) EXT3-fs error (device sda1): ext3_readdir: bad entry in directory #143278260: rec_len % 4 != 0 - offset=0, i...

...5 and acl v2.2.23-1 on a Sunblade 100 (sparc). In a few months we have experienced for several times that an ext3 filesystem is remounted as read-only (this is due to the option "errors=remount-ro" in /etc/fstab). Sometimes there is no error in log files but sometimes we see: kernel: init_special_inode: bogus i_mode (3016) kernel: init_special_inode: bogus i_mode (3125) kernel: init_special_inode: bogus i_mode (3144) kernel: init_special_inode: bogus i_mode (3231) kernel: init_special_inode: bogus i_mode (3423) kernel: init_special_inode: bogus i_mode (3452) In the former case (no error in the l...

(sort-of xposted from linux-kernel) Hi, I am wondering how to interpret this error message, which popped up on a 2.4.26 SMP x86 box two days ago: EXT2-fs: corrupt root inode, run e2fsck init_special_inode: bogus imode (37316) EXT2-fs: corrupt root inode, run e2fsck init_special_inode: bogus imode (37316) EXT2-fs: corrupt root inode, run e2fsck The problem is, the error message doesn't indicate *which* filesystem we are talking about, and I have three mounted: 1 ext2 and 2 ext3. The ext2 is on...

...270 based processor (on a single board computer) which makes the processor vulnerable to bit flips. One such bit flips seems to have corrupted the file system. The debug port on the board (it is a single board computer) had the following message when i think the FS corruption occured : <7>init_special_inode: bogus i_mode (33061) init_special_inode: bogus i_mode (30071) init_special_inode: bogus i_mode (34065) init_special_inode: bogus i_mode (30061) init_special_inode: bogus i_mode (33061) init_special_inode: bogus i_mode (30071) After this happened, directories like bin etc. were corrupted ( I...

...node->i_mode |= S_IFSOCK; inode->i_rdev = OCFS_NODEV; -#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,0) - dev = MKDEV (fe->dev_major, fe->dev_minor); -#else - kdev = MKDEV (fe->dev_major, fe->dev_minor); -#endif - -#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,0) - init_special_inode (inode, inode->i_mode, dev); -#else - init_special_inode (inode, inode->i_mode, - kdev_t_to_nr(kdev)); -#endif + init_special_inode (inode, inode->i_mode, + MKDEV(fe->dev_major, fe->dev_minor)); break; } default:

When trying to move my root to a btrfs filesystem, I found a missing feature (or a bug). It's not possible to create device files. To reproduce, run this on a btrfs filesystem: mknod test c 1 1 result: mknod: `test': Operation not permitted Frank

...3_file_operations; inode->i_mapping->a_ops = &ext3_aops; err = ext3_add_nondir(handle, dentry, inode); - ext3_mark_inode_dirty(handle, inode); } ext3_journal_stop(handle, dir); return err; @@ -490,7 +492,6 @@ static int ext3_mknod (struct inode * di if (!IS_ERR(inode)) { init_special_inode(inode, mode, rdev); err = ext3_add_nondir(handle, dentry, inode); - ext3_mark_inode_dirty(handle, inode); } ext3_journal_stop(handle, dir); return err; @@ -934,7 +935,6 @@ static int ext3_symlink (struct inode * } inode->u.ext3_i.i_disksize = inode->i_size; err = ext3_add_non...

...used on NationalGeode embedded board. The following entry was used in fstab (I know, may be stupid, but should not crash the filesystem?) /dev/hda1 / ext2 defaults,sync 1 1 After the board is switched off, it does not boot anymore, the following message is displayed: init_special_inode: bogus imode (0) EXT3-fs: invalid journal inode. After I have removed "sync" and changed ext2 to ext3 it is working. But I have a feeling that actual problem was "sync", not "ext2" because the disk was anyway mounted as ext3. I have images of a "good" disk...

hello, Chris In the next several months, I will have a lot of spare time. I will be happy if you assign some work to me. I have learn linux kernel for years but only fix a few small bugs in IP stack. In the past few months, I read some EXT4/VFS codes. I began reading source of btrfs ten days ago and have read it twice now. Regards YZ

If we have particularly full nodes, we could call btrfs_node_blockptr up to 32 times, which is 32 pairs of kmap/kunmap, which _sucks_. So go ahead and map the extent buffer while we look for readahead targets. Thanks, Signed-off-by: Josef Bacik <josef@redhat.com> --- fs/btrfs/ctree.c | 23 +++++++++++++++++++++-- 1 files changed, 21 insertions(+), 2 deletions(-) diff --git

...ase WDIOC_GETBOOTSTATUS: return put_user(0, p); case WDIOC_SETOPTIONS: diff --git a/fs/efs/inode.c b/fs/efs/inode.c index 89e73a6f0d36..64f3a54a0f72 100644 --- a/fs/efs/inode.c +++ b/fs/efs/inode.c @@ -161,11 +161,10 @@ struct inode *efs_iget(struct super_block *super, unsigned long ino) init_special_inode(inode, inode->i_mode, device); break; default: pr_warn("unsupported inode mode %o\n", inode->i_mode); goto read_inode_error; - break; } unlock_new_inode(inode); return inode; diff --git a/fs/ocfs2/cluster/tcp.c b/fs/ocfs2/cluster/tcp.c index 79a231...

...ase WDIOC_GETBOOTSTATUS: return put_user(0, p); case WDIOC_SETOPTIONS: diff --git a/fs/efs/inode.c b/fs/efs/inode.c index 89e73a6f0d36..64f3a54a0f72 100644 --- a/fs/efs/inode.c +++ b/fs/efs/inode.c @@ -161,11 +161,10 @@ struct inode *efs_iget(struct super_block *super, unsigned long ino) init_special_inode(inode, inode->i_mode, device); break; default: pr_warn("unsupported inode mode %o\n", inode->i_mode); goto read_inode_error; - break; } unlock_new_inode(inode); return inode; diff --git a/fs/ocfs2/cluster/tcp.c b/fs/ocfs2/cluster/tcp.c index 79a231...

Hi, Is the http://xenbits.xensource.com/linux-2.6-xen.hg tree still being updated? if not, what''s the preferred Linux tree to track that has all of the Xen bits? Thanks, Muli _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel