similar to: ML9.0:file system completely crashed ext3,"could not find mime type",kde3.0.3

Hello all, I have a few strange errors in my messages log I can't fix. My system works great, it just bugs me that I have error (or apparent errors) that I don't know about. I get automount errors regurlarly (daily) that are reflected in the last four lines of the log file excerpt below. My misc and net directories are there, but I can't write to them either. The properties say that

I wanted to boot gentoo on xen, but it doesn''t work. What can I do? Booting ''Xen 3.0.0 / Linux 2.6.12.5'' root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /xen.gz dom0_mem=131072 com1=115200,8n1 [Multiboot-elf, <0x100000:0x641cc:0x27e34>, shtab=0x18c078, entry=0x100000] module /vmlinuz-2.6.12.5-xen-0 root=/dev/md0

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]

Hi, i am seeing a crash in ext3_new_block quiet often today on 2.2.19 0.0.7a fsck 1.21 ksymoops 2.3.4 on i686 2.2.19. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.2.19/ (default) -m /boot/System.map-2.2.19 (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the

Hi, I have read this thread and want to say that I have expirienced the same problem. Once, when I was loged in, one of my filesystems ( root filesystem :( ) became read-only with the same symptoms. But results was more tragic. Almost in each directory avg. 10% of files had incorrect attributes, owner, links, etc. But filenames was correct. So, I was obliged to re-create root filesystem :(

Hi folks, Backing up a host as noted below im getting over and over again the same issue on actual kernel, details: - Backup host has a pci/usb2.0 card, with a 250gb usb 2.0 disk attached, - Celeron 900 family - Remote host, local console from boot linux rescue: # dd if=/dev/hda conv=sync,noerror | ssh -c blowfish root at 192.168.0.6 "dd of=/media/backup/vol-hda.raw.img" - Backup

After a bit of searching through these archives I haven't found quite my problem described yet, so let me bounce this off you guys: Red Hat 7.2, I run up2date whenever patches come out; right now I'm using kernel 2.4.9-21. Things have been quite pleasant for several months, but in the last week I have begun receiving the following error messages: Feb 22 08:06:27 medmeta kernel:

A brand new system setup with RH 7.3 is still Oopsing after every X hours. The problem started after about 1 week without errors. Sometimes everything is locked, sometimes still messages are written to /var/log/messages. Sometimes other processes keep running (can still ping the machine) I upgraded the kernel to 2.4.18-19.7.x, changed the memory, but still got problems. When I read all sort of

Hi. I was using ext3 0.0.1 without any problems in the last 33 days (same boot). / was still ext2, but I changed /etc/fstab to ext3. /home/ftp/pub/ is ext3. I mounted /home/ftp/pub/slakware/bare.i with loopback in /mnt/floppy/. After some time: ==> /var/log/syslog <== Jul 4 09:40:51 pervalidus kernel: Assertion failure in ext3_prepare_write() at inode.c:934: "handle != 0" Jul 4

Just wondering if someone could help me debug this: I was moving data from an ATARAID (via Promise FastTrack100 Controller) into the LVM device below: 58,1: # cat /proc/lvm/VGs/foo3/LVs/bar name: /dev/foo3/bar size: 476315648 access: 3 status: 1 number: 0 open: 1 allocation: 0 device: 58:01 # /sbin/pvscan pvscan -- reading all physical volumes

I recently bought 2 different USB flash disks. These are some cheap no-name devices. Their parameters: bytes C/H/S ID 4194304512 509/255/63 Vendor: Generic Model: USB Flash Drive Rev: 1.00 ANSI SCSI revision: 02 4288676352 1023/132/62 Vendor: USB Model: USB 2.0 Rev: 1.00 ANSI SCSI revision: 02 When I put a FAT32 filesystem on them,

Greetings! Need your help fellow penguins! Strange behavior with fsck.ext3: how to remove a long orphaned inode list? After copying data over from one old RAID to another new RAID with rsync, the dump command would not complete because of filesystem errors on the new RAID. So I ran fsck.ext3 with the -y option and it would just run in an infinite loop restarting itself and then trying to correct

On 2013-08-29, at 7:48 PM, Richards, Paul Franklin wrote: > Strange behavior with fsck.ext3: how to remove a long orphaned inode list? > > After copying data over from one old RAID to another new RAID with rsync, the dump command would not complete because of filesystem errors on the new RAID. So I ran fsck.ext3 with the -y option and it would just run in an infinite loop restarting

Red Hat 2.2.19-6.2.12 + 0.0.7a + https://listman.redhat.com/pipermail/ext3-users/2001-November/002258.html (not tuned in /proc yet) + journal 4MB on each fs + 6 ext3 fs on raid1 (hda+hdc) + 1 ext3 fs on another disk not on raid1 (hdd) While untarring (tar zxf) a file that was on a ext3/raid1 onto hdd I got: ksymoops 2.3.4 on i686 2.2.19-6.2.12.g1. Options used -V (default) -k

Is there a reason why an ext3 root partition cannot be copied to an alternate partition using the "dd" command? The dd is copying the mounted root partition into an alternate partition that is not mounted. The dd returns success, but the fsck on that partition fails with errors as follows: ----------------- fsck 1.37 (21-Mar-2005) /dev/Active_Update/root2: recovering journal

Dear R core team Please apologize for posting the same question twice on R-help and R-devel. Since I was not sure which list is appropriate I tried R-help (Tue Mar 22), but got no answer. Now I do not know if the formulation of my question was unclear or the question is not so easy to answer or to easy (what I do not hope). My problem: I create a new S4 class, containing one slot, data (of

Dear R gurus I've a question concerning the transformation of a new S4 class (that I defined) and the existing class "POSIXlt". I did the following: ## Definition of the new class: setClass("dtime", representation(data = "POSIXlt"), prototype(data = as.POSIXlt("2004/06/01"))) ## Transformation between the new class "dtime"

Just to make sure somebody reacts (please) I'm forwarding this. Please cc me on replies as I'm not subscribed to this list. -------- Original Message -------- Subject: [RESEND] 2.4.20: ext3: Assertion failure in journal_forget()/Oops on another system Date: Wed, 04 Dec 2002 21:27:31 +0100 From: Andreas Steinmetz <ast@domdv.de> To: Linux Kernel Mailing List

I'm constructing a raid 5 of 3 160gb sata drives. They're connected to a promise sx4 150 card, using the kernel drives (not promise's binary only drivers). the raid builds fine, as does creation of the ext3 filesystem. however, if i then run e2fsck (with the -f option since the filesystem is brand new) i get thousands of these type of errors: Inode 15461 has imagic flag set.

I am running Mandrake 9.0 and have installed OpenLDAP by using RPMDrake and installing it from a package included on the CD's. When I run ./configure it never finds the installation. How can I fix this? Is OpenLDAP absolutely required to get Samba working with Windows 2003? Thanks Matt