similar to: journal aborting and remounting /boot as ro

While compiling two kernels and untarring a third, my root fs was remounted r/w and I got the following in dmesg (kernel 2.4.19-pre9): EXT3-fs error (device ide0(3,2)) in ext3_new_inode: error 28 Aborting journal on device ide0(3,2). ext3_abort called EXT3-fs abort (device ide0(3,2)): ext3_journal_start: Detected aborted journal. Remounting filesystem read-only Remounting filesystem read-only

How can I do this? I have a samba server running on RedHat Linux. The server is actually a dual boot machine, and has Windows drives which I have mounted under Linux, so that /mnt/dosC is the C: drive when booted under DOS. Also, this machine has a Zip drive connected to it and known as /mnt/zip. >From a Windows 98 machine connected to this machine, connecting through Samba, I can see these

Getting this oops on one of our production servers pretty much hangs the server. Do we have a corrupted Journal? how would ewe rebuild it? Any idea how to recover from it? Assertion failure in journal_bmap() at journal.c:636: "ret != 0" invalid operand: 0000 CPU: 0 EIP: 0010:[journal_bmap+70/96] Not tainted EIP: 0010:[<c016b646>] Not tainted EFLAGS: 00010282

ext3 is having big problems on my x86-64 system. An ext3 partition has just gone crazy, with the following messages in dmesg: EXT3-fs error (device hda3): ext3_readdir: bad entry in directory #4603905: rec_len % 4 != 0 - offset=0, inode=2507704792, rec_len=42, name_len=0 Aborting journal on device hda3. ext3_abort called. EXT3-fs abort (device hda3): ext3_journal_start: Detected aborted journal

Hi, Apologies, this is going to be quite long - I'm going to provide as much info as possible. I'm running a system with ext3 fs on software RAID. The RAID set-up is as shown below: jlm@nijinsky:~$ cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid5] read_ahead 1024 sectors md0 : active raid1 hdc1[1] hda1[0] 96256 blocks [2/2] [UU] md5 : active raid1 hdk1[1] hde1[0]

On bootup, it seems CentOS automatically mounts the floppy drive to /media/floppy. Is there a way to stop this from happening, short of removing the floppy drive from the system (as I don't use it)? Thanks, Ash Christopher -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi there, I'm using RH7.2 (with the 2.4.9-30 kernal and it's required components) as a base for a server system running kernel 2.4.18. I've gone to this version to get around non-performing aic7xxx drivers in the stock 7.2 kernels, and updated gigabit ethernet drivers. I have a raid unit (Medea) attached to an Adaptec 3916, coming up as sdb. It has 2kb blocks, but the fault

Hi, Thanks to everyone involved in the Xen project. I think it is great and can''t wait to get my hands dirty with it. In the meantime, I cannot boot Dom0 on an ibm x335 and I am not sure what the problem is. Any insights are welcome. Here is what my grub.conf file looks like: title Fedora Core (2.6.8-1.521) root (hd0,0) kernel /vmlinuz-2.6.8-1.521 ro root=/dev/sda9

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I was a thread on the list archive from a few months ago, about a user who had added 'data=journal' in /etc/fstab. The system stopped working properly because the device couldn't be remounted rw after fsck ran - because ext3 wouldn't allow changing the journalling options on remount. I can understand that changing data=x in general

Hi! Today I switched over to devfs. I'm on Debian unstable, installed devfsd, installed a kernel with devfs support and "devfs mount on boot". Reboot, devfs is being used. All over a sudden, dmesg reports: Linux version 2.4.21-ac1 (root@hummus) (gcc version 3.3 (Debian)) #1 Sun Jun 15 19:06:13 CEST 2003 ... kjournald starting. Commit interval 5 seconds EXT3-fs: mounted

Hello, I am attempting to fit a non-linear model (Von Bertalanffy growth model) to fish length-at-age data with the purpose of determining if any of the three parameters differ between male and female fish. I believe that I can successfully accomplish this goal assuming an additive error structure (illustrated in section 1 below). My trouble begins when I attempt this analysis using a model

Hi, yesterday I upgraded my kernel to 2.4.15-pre6 (after months of using only ac-kernels) and had my first ext3-error since 0.0.3 . syslog tells me : Nov 20 18:16:31 enterprise kernel: EXT3-fs error (device ide0(3,9)): ext3_readdir: bad entry in directory #47390: inode out of bounds - offset=0, inode=404363549, rec_len=4096, name_len=23 and the system remounted /usr to ro. I don't have

I am using the "predict" function on a support vector machine (svm) object, and I don't understand why I can't predict on a dataset with more observations than the training dataset. I think this problem is a generic "predict" problem, but I'm not sure. The original svm was fit on 50 observations.

Wondering if anyone here might better be able to diagnose an issue we're seeing, or point me to some guidelines for this sort of thing. There are two machines with identical hardware, both running Red Hat 7.3's stock SMP kernel (required due to third party software). Both have come down with the same symptoms after having run fine for a number of months. The initial errors were these:

Several people already reported this at linux-kernel and elsewhere with no answers, I thought perhaps this would be a more adequate forum... [1.] One line summary of the problem: After I/O, journal is aborted and filesystems made read-only. [2.] Full description of the problem/report: One can't anymore write to the affected file systems. Upon investigation, ext3fs journal was aborted

Hi! I noticed yet another dying IBM drive in one of my servers, producing IDE + "standard" ext3 error messages (happened during the start of a new journal methinks): ext3_reserve_inode_write: aborting transaction: Journal has aborted in __ext3_journal_get_write_access<2>EXT3-fs error (device ide5(57,1)) in ext3_reserve_inode_write: Journal has aborted which clearly shows that

Hi Greg, Really, the first step to install filesystem it with support ACL. It looks at my archive: LABEL=/ / ext3 defaults,acl 1 1 LABEL=/boot /boot ext3 defaults 1 2 LABEL=/data /data ext3 defaults,acl 1 2 none /dev/pts devpts gid=5,mode=620

A patch that implements acls on ext3 for kernel 2.2.x is available at http://moldybread.net/patch/kernel-2.2/ It looks to be stable. Beat it, break it.

To All any help would be appreciated, I am running Redhat Linux Advanced Server release 2.1AS I do a uname -a and get the following 2.4.18-14smp I have samba 2.2.7-3.7.2 I have setup a share going from linux to windows and it seems to work fine up to 2 gig when it hits 2 gig it stops. Do I need to upgrade to a newer release of samba. Thank You Ralph Ralph Feole LogistiCare, Inc.

Specs: Oracle 9.2.0.4 OS is Redhat AS2.1 ocfs-2.4.9-e-summit-1.0.12-1 ocfs-tools-1.0.10-1 ocfs-support-1.0.10-1 ocfs-2.4.9-e-enterprise-1.0.12-1 Shared Storage: Dell/EMC CX600 naviagentcli-6.19.0.4.14-1.noarch.rpm PowerPath 4.4 My system was originally installed by Dell. Since then I've upgraded the OCFS and a few other pkgs. But ever since the beginning the ocfs drives mounted on boot.