similar to: Strange fsck.ext3 behavior - infinite loop

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

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

On Fri, Aug 30, 2013 at 12:07:22PM -0600, Andreas Dilger wrote: > > > [root@myhost /]# mkfs.ext3 /dev/sda1 > > mke2fs 1.35 (28-Feb-2004) > > First thing I would suggest is to update to a newer version of e2fsprogs, since this one is 9+ years old and that is a lot of > water under the bridge. That's definitely good advice, but even with e2fsprogs 1.35, if e2fsck -f is

Hi, I would appreciate if somebody could help me with this small issue... I have a dataframe like this (originaly has more than 100 000 rows): > subz jul time dtime fix ddawn ddusk day 101608 15006 2011-02-01 19:14:49 19.24694 noon 7.916667 19.88333 1 101609 15006 2011-02-01 19:24:49 19.41361 midnight 7.916667 19.56667 1 101610 15006 2011-02-01

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.

Dear All, I have a pair of .cpp and .def file can be compiled using VC++ and works perfectly well in S-PLUS. I wanted to do the same for R; so I followed the guidline given in "Building from a source-code library under Windows" as much as possible and manage to compile them using VC++ and call it from R. But it gives different answer from the one called from S-Plus. I know that I did

Mandrake Linux 9.0 here: I installed alsa-utils from CD1 with MCC:Software Install: in /var/log/syslog these error messages appeared (SEE BELOW): "XT3-fs error (device ide0(3,2)): ext3_new_block: Allocating block in system zone - block = 294914" Then I rebooted (because I wanted to boot in runlevel 3 to see whether I could play sound..., not relevant here). Error bootmessages appeared

i posted on rhel list about proper creating of 6tb ext3 filesystem and tuning here.......http://www.redhat.com/archives/nahant-list/2006-November/msg00239.html i am reading lots of ext3 links like...... http://www.redhat.com/support/wpapers/redhat/ext3/ http://lists.centos.org/pipermail/centos/2005-September/052533.html http://batleth.sapienti-sat.org/projects/FAQs/ext3-faq.html ............but

Hi All, > act_2 Date Dtime Hour Min Second Rep 51 2006-02-22 14:52:18 14 52 18 useractivity_act 52 2006-02-22 14:52:18 14 52 18 4 55 2006-02-22 14:52:49 14 52 49 4 57 2006-02-22 14:52:51 14 52 51 4 58 2006-02-22 14:52:52 14 52 52 3 60 2006-02-22 14:54:42 14 54

Hi All, > act_2 Date Dtime Hour Min Second Rep 51 2006-02-22 14:52:18 14 52 18 useractivity_act 52 2006-02-22 14:52:18 14 52 18 4 55 2006-02-22 14:52:49 14 52 49 4 57 2006-02-22 14:52:51 14 52 51 4 58 2006-02-22 14:52:52 14 52 52 3 60 2006-02-22 14:54:42 14 54

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I got an IDE-drive which decided to get broken. Part of the extended partition table was lost, but I was able to recover it, so I could reach the ext3 filesystem with a size of about 135 GB. I made a copy of it (luckily the ISP doesn't seem to need the broken drive urgently hehe) and ran fsck on that copy. The first time I ran fsck I

Greetings, useRs. Does anybody have replication of the examples from the RMS book by Harrell coded in R? I find that most the code does not work and it takes too much time to debug. For example from p.276 > age.t <- w[,"age"] > f.full <- lrm(cvd~scored(rx)+rcs(dtime,5)+age.t+wt.t+pf.t+hx+sbp+ekg.t+sz.t+sg.t+ap.t+bm+hg.t,x=T,y=T) Error in model.frame.default(formula = cvd ~

Hi All, > act_2 Date Dtime Hour Min Second Rep 51 2006-02-22 14:52:18 14 52 18 useractivity_act 52 2006-02-22 14:52:18 14 52 18 4 55 2006-02-22 14:52:49 14 52 49 4 57 2006-02-22 14:52:51 14 52 51 4 58 2006-02-22 14:52:52 14 52 52 3 60 2006-02-22 14:54:42 14 54

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 No-one out there who can give me any tips for this? (Then the space to do experiments will finally be used in other ways. And I hope this mail won't be consired to impolite...) On Mon, 6 Dec 2004 15:23:15 +0100 Milan Holz?pfel <lists at mjh.name> wrote: > Hello, > > I got an IDE-drive which decided to get broken. Part of

Wow, it takes a really long time to make a 2TB ext2fs. Are there better-than-default options that could be used for a large filesystem? mke2fs 1.34 (25-Jul-2003) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 244203520 inodes, 488382016 blocks 24419100 blocks (5.00%) reserved for the super user First data block=0 14905 block groups 32768 blocks per group,

Hello, I have: CentOS4.1 x86_64 directly-attached Infortrend 9TB array QLogic HBA seen as sdb GPT label created in parted I want one single 9TB ext3 partition. I am experiencing crazy behavior from mke2fs / mkfs.ext3 (tried both). If I create partitions in parted up to approx 4,100,000 MB in parted, mkfs.ext3 works great. It lists the right number of blocks and creates a filesystem that fills

While I untar a large archive on xfs , ext3 (ver 1.3 and ver 1.4) file systems , on ppc processor and kernel ver 2.6.21 , I get an error. Also sometimes, on ext3 (1.3 and 1.4) the file system goes read-only while untarring. The same tar file when untarred on a i386 machine works properly. ERROR: -------------- tar: Skipping to next header gzip: stdin: invalid compressed data--crc error tar:

About two weeks ago i was whining about an inode that got lost, now i'm going to whine more about strange things happening here. A matroxfb just oopsed on me (thats not strange), the machine got unusuable, so i logged in from another and got the idea to touch /forcefsck. Upon reboot, fsck said that some inodes are in use but have dtime set and that some files are illegal sockets. Now this

Over the last two days we've been seeing a fair bit of this: ---- # ls -laR > /dev/null ... ls: ./server2/b/user/bxyz/392.: Input/output error ---- This is with the latest htree patches applied to 2.4.19, and latest e2fsprogs-test, on a dual AMD system, with 5x73GB SCSI drives on a MegaRAID controller. We're using the gcc 2.96 that comes with RH7.3. esfsck shows "Inodes that

Hi, i am seeing something interesting since the upgrade to 2.2.19/0.0.7a - I am experimenting with the am930 wireless driver and i am crashing on module exit. Everytime i reboot afterwards the var fs on /dev/hda8 is inconsistent [...] Checking all file systems... Parallelizing fsck version 1.21-WIP (01-Jun-2001) /dev/hda7: recovering journal /dev/hda7: clean, 39160/320640 files, 354596/640702