similar to: Journal Aborts in VMware ESX (Filesystem Corruption)

Hi, I'm running kernel 2.6.8-15, lvm2 v2.01.04-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:

Hey, I've a problem with an ext3 filesystem and don't know how to fix it or find the failure :( The Hardware: Tyan mainboard, AMD Athlon CPU, ARECA ARC-1120 RaidController Raid5 with 400GB Seagate HD's, 756 MB Ram, other harddisks for system, network and avm isdn controller. Couse of the filesystem problems I run memtest and found one bad memory module which I replaced yet. The

The difference between kdev_t and dev_t in 2.4 is rather theoretical, no need to clutter up the source for it. Index: src/inode.c =================================================================== --- src/inode.c (revision 969) +++ src/inode.c (working copy) @@ -1877,11 +1872,8 @@ case OCFS_ATTRIB_FIFO: case OCFS_ATTRIB_SOCKET: { -#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,0)

Hello, I am doing some testing on a PXA270 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:

(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

Hi all, I have a bunch of mail servers running postfix (external smtp), qmail (LDA) and courier IMAP/POP. Frequently, Ext3 filesystem goes into read-only mode forcing recovery using fsck. Below are the errors we have seen so far on these systems and those systems config. The ext3 errors are common in many cases. 1. Red Hat Enterprise Linux Server release 5.2 (Tikanga) 2.6.18-92.1.10.el5

In reflink we update the id info in the disk but forget to update the corresponding information in the VFS inode. So update them accordingly in case we want to preserve the attributes. Reported-by: Jeff Liu <jeff.liu at oracle.com> Signed-off-by: Tao Ma <tao.ma at oracle.com> --- fs/ocfs2/refcounttree.c | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git

I got this error in my log reports this morning, from the machine I use as my firewall. This is the first time it has occurred, but the machine is running a very new kernel: Linux fendrian.rimspace.net 2.6.0-test11-fendrian #1 Wed Dec 10 22:25:59 EST 2003 i486 GNU/Linux The kernel was up to date as per the CVS repository at that point. This was just before the CDROM_SEND_PACKET IOCTL fix went

When CONFIG_EXT3_FS_POSIX_ACL is not defined, ext3_init_acl() is an inline function in fs/ext3/acl.h which doesn't check if a file is a symlink before applying umask. I've always liked my acls to be available (so never noticed), but came across this recently when trying to explain why RedHat Enterprise 3's BOOT kernel creates symlinks 755 during kickstart. I'm *assuming* this is

when we fall back to buffered write from direct write, we call __generic_file_aio_write but that will end up doing direct write even we are only prepared to do buffered write because the file has O_DIRECT flag set. This is a fix for https://bugzilla.novell.com/show_bug.cgi?id=591039 revised with Joel's comments. --- fs/ocfs2/file.c | 23 ++++++++++++----------- 1 files changed, 12

Hi, i am seeing an oops (every couple of days) on a UP PII system with SCSI disks, Kernel 2.2.19 and ext3 0.0.6b. All oops output passed the klogd thus i cant anymore pipe it through ksymoops - I ensured klogd got the correct System.map so the result should be reliable. Apr 25 17:03:10 Unable to handle kernel paging request at virtual address 8efd1fc8 current->tss.cr3 = 0981e000, %%cr3 =

No material changes are made. --- Makefile | 10 +- convert.c => convert/convert.c | 803 +--------------------------------------- convert/convert.h | 76 ++++ convert/ext2.c | 791 +++++++++++++++++++++++++++++++++++++++ 4 files changed, 873 insertions(+), 807 deletions(-) rename convert.c => convert/convert.c (74%) create mode

Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org> --- fs/btrfs/inode.c | 11 +---------- 1 files changed, 1 insertions(+), 10 deletions(-) diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c index 4deb280..ae4f64c 100644 --- a/fs/btrfs/inode.c +++ b/fs/btrfs/inode.c @@ -4145,16 +4145,7 @@ static struct inode *btrfs_new_inode(struct btrfs_trans_handle *trans, if (ret != 0) goto

Al writes: > On Thu, 22 Mar 2001, Andreas Dilger wrote: > > If this is the case, then all of the other zero initializations can be > > removed as well. I figured that if most of the fields were being > > zeroed, then ones _not_ being zeroed would lead to this problem. > > Other zero initializations in inode->u certainly can be > removed, but whether it's

Add a mount option user_subvol_rm_allowed that allows users to delete a (potentially non-empty!) subvol when they would otherwise we allowed to do an rmdir(2). We duplicate the may_delete() checks from the core VFS code to implement identical security checks (minus the directory size check). Signed-off-by: Sage Weil <sage@newdream.net> --- fs/btrfs/ctree.h | 1 + fs/btrfs/ioctl.c |

A change was made to ext3 in 2.4.20-pre9 which will cause the filesystem to run ext3_mark_inode_dirty() against a freed inode. This will occur when an application attempts to add a new file/directory to the filesystem and encounters space or inode exhaustion. The results of this are unpredictable. Usually, nothing happens. But it can cause random memory corruption on SMP, and the kernel will

I have been using ext3 filesystem from 2.4.17 kernel in the default "ordered" mode on an 64 MB SanDisk compactflash. The disk itself was 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

Index: namei.c =================================================================== --- namei.c (revision 968) +++ namei.c (working copy) @@ -526,7 +526,7 @@ status = -EBUSY; - if (!empty_dir(inode)) { + if ( S_ISDIR (inode->i_mode) && !empty_dir(inode)) { LOG_TRACE_STR ("dentry is not empty, cannot delete"); goto

Hi all. I posted this to LKML, but might get a faster reply if I go direct to you. I haven't subscribed, so please reply to me too... I began a bk export -du patch and shortly afterwards a cp -arl on the kernel source tree. The latter got stuck in ext3_lookup iget_locked find_inode_fast __wait_on_freeing_inode schedule The box is running 2.6.8.1 with SMP, HT scheduler and preempt (can

Hi, I added additional storage to my domU using xm block-attach and tap:aio. Then increased my root device (using vgextend, lvextend and resizefs) which is / or /dev/mapper/VolGroup00-LogVol00. Everything worked fine util I did "xm save domid test1.img" This stopped my domU. And now when I run: xm create domU -c , I am seeing -- Scanning logical volumes Reading all physical volumes.