similar to: "ext2fs_check_if_mount: No such file or directory while determining whether" messages

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 :(

Is there an updated version of the fileutils df that will show mounted ext3 partitions? I'm using fileutils-4.1. -- Curtis Hogg [buckminst@inconnu.isu.edu] ---------------------------------------------- T-shirt Of The Day: I'm the person your mother warned you about. ---------------------------------------------- Email 1 - buckminst@inconnu.isu.edu Email 2 - buckminst@hotmail.com WWW -

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

Hi. IIRC, I had the same problem with 2.4.3 and ext2, I'm not sure if with the same directory entry, but at the time fsck fixed without any problems. I only know that the error again is with my Mozilla sources. The Mozilla sources are in another partition. I used lndir from my root fs to symlink everything and build it. At some point c++ segfaulted (happens a lot with my GCC 3.0), and I had

Hi, I have a severe filesystem crash on a machine with a single ext3 filesystem. It is the second time that this happens to me (on two different machines that are identical in hardware setup and mostly in software - I cloned them when I started to work). It looks like the journal (or something else, i am not an expert here) has gone wild and overwritten loads of inodes. I have a single filesys

I have many errors of this type in my logs: 2 * postfix/pipe[21511]: BC8DD3356A: to=<*****@******>, relay=dovecot, delay=1001, status=bounced (Command time limit exceeded: "/usr/local/dovecot-1.0-rc2/libexec/dovecot/deliver") My command time limit is 1000s in postfix (more than 15 minutes) After many check, I found that a lots of this error is not really an error. The mail is

Hi, I'm encountering a strange situation. I'm writing to an ext3 filesystem mounted like this: /dev/scsi/host2/bus0/target0/lun0/part3 on /tmp/volumes/md0 type ext3 (rw,noatime,data=ordered) with the physical device being a FC-connected RAID (IBM DF4000) no software raid personality is used I'm using 2.4.18-19.7 My test program writes files in a loop, with the essential system

Hi, I am trying to boot from an external USB hard drive (partition 1: Windows, partition 2: primary/bootable ext3). I took the kernel-image-2.6.8-1-368.deb and created a new initrd with all modules, root=/dev/sda2 and Busybox (mkinitrd failed with my own kernel ;-) isolinux.cfg contains: PROMPT 1 DEFAULT sda2 LABEL sda1 KERNEL vmlinuz APPEND initrd=initrd ramdisk=16432k root=/dev/sda1

Hello everyone! I''m new with Xen and i''ve been dealing with the same error the last week. I''m pretty much lost, i don''t know what else to do so i ask for your help. In my case i installed Xen on a amd64 Pc, with Gentoo. I installed the following packages: xen, xen-tools and xen-sources from the gentoo repositories. I''m using 2.6.31-xen-r10 gentoo

Hi everyone, I have a udev rule file that contains a singular rule: SUBSYSTEM=="block", ACTION=="add|change", ENV{ID_VENDOR}=="*Google*", ENV{DEVTYPE}=="disk", ATTR{queue/scheduler}:="noop" When I use a Google Cloud instance and boot it, things work as expected and /dev/sda (a persistent disk) uses the noop scheduler. If the instance also has a

Hi all, This is my first post to the list. My first real major issue with xen. I started on 3.4.2 and upgraded to 4.0.1 without issues. Now I just attempted to go to 4.1.0 and I got the following errors in my log. # cat /var/log/xen/xend-debug.log Xend started at Fri Apr 1 13:51:15 2011. cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory cat:

Package: xen-utils-4.0 Version: 4.0.1-2 Severity: normal Tags: squeeze I have 3 VM running. I have upgraded debian squeeze to 6.0.1 (new kernel package 2.6.32-31) and restarted my server. VM were still running. After reboot I could not start xend service (from init.d). I got following errors: kern.log: Mar 22 15:07:30 router kernel: [53888.212756] xenstored[7232]: segfault at 7fff056b5ff8 ip

Hello I did the following commands and resulted in a segmentation fault. [root@localhost ~]# mkfs.btrfs /dev/sda6 WARNING! - Btrfs Btrfs v0.19 IS EXPERIMENTAL WARNING! - see http://btrfs.wiki.kernel.org before using fs created label (null) on /dev/sda6 nodesize 4096 leafsize 4096 sectorsize 4096 size 46.93GB Btrfs Btrfs v0.19 [root@localhost ~]# mount /dev/sda6 /mnt/btra [root@localhost ~]#

On 01.09.20 18:21, Helge Deller wrote: > On 01.09.20 17:22, James Bottomley wrote: >> On Tue, 2020-09-01 at 16:05 +0100, Matthew Wilcox wrote: >>> On Tue, Sep 01, 2020 at 07:52:40AM -0700, James Bottomley wrote: >>>> I think this looks mostly OK, except for one misnamed parameter >>>> below. Unfortunately, the last non-coherent parisc was the 700

On 01.09.20 17:22, James Bottomley wrote: > On Tue, 2020-09-01 at 16:05 +0100, Matthew Wilcox wrote: >> On Tue, Sep 01, 2020 at 07:52:40AM -0700, James Bottomley wrote: >>> I think this looks mostly OK, except for one misnamed parameter >>> below. Unfortunately, the last non-coherent parisc was the 700 >>> series and I no longer own a box, so I can't test

Hi there. I cannot start xen, I''m getting this error System: Linux netwarrior 2.6.31.13 #5 SMP Wed Jun 30 13:25:47 ART 2010 x86_64 AMD Athlon(tm) II X4 630 Processor AuthenticAMD GNU/Linux xend.log le "/usr/lib64/python2.6/site-packages/xen/xend/xenstore/xstransact.py", line 355, in Mkdir complete(path, lambda t: t.mkdir(*args)) File

Hi all, I have a following problem: - Remus network buffering doesn''t work. It seems to be because of no vif is reported by the function server.xend.domain on line 29 of /usr/local/lib/python2.7/dist-packages/xen/remus/vm.py (seen using pdb) : 27 if domid: 28 try: 29 self.dominfo = server.xend.domain(domid, ''all'') >

I have a couple development servers running centos 6.3 64bit that have LSI 9211-8i SAS2 controllers connected to a SAS2 backplane. these work fine with SATA hard disks (populated with a bunch of 3TB SATA drives)... I'm trying to install a OCZ Vertex3 SSD on each of the two servers to do some ssd caching tests... system sees the drive, so I do the following... # parted -a min

i'm acessing a centos box via ssh, is there any way that i can find out the hard drive info, such IDE/SATA, format, size, make & model, etc...? thanks

My manager's workstation is C 7.4, and it started screaming yesterday about issues with ata5. Except that he has one internal and one external drive, and a DVD. Anyone have clues as to what could be causing this, or where to start looking? He's rebooted it, and before that, I tried rescan-scsi-bus.sh, with no joy. mark