Displaying 20 results from an estimated 80000 matches similar to: "Urgent question"
2014 Sep 21
1
Re: Possible bug in mkfs.ext3
On 09/20/2014 12:07 AM, Andreas Dilger wrote:
> On Sep 19, 2014, at 7:56 PM, jd1008 <jd1008@gmail.com> wrote:
>> I am reporting this on the advice of the Fedora Users Mailing List Member.
>>
>> This the mailing list exchange outlining the problem with specifying -S to mkfs, and it's subsequent consequences when fsck is run.
>>
>> I am reporting this per
2014 Apr 18
0
Re: Many orphaned inodes after resize2fs
On Fri, Apr 18, 2014 at 06:56:57PM +0200, Patrik Horn?k wrote:
>
> yesterday I experienced following problem with my ext3 filesystem:
>
> - I had ext3 filesystem of the size of a few TB with journal. I correctly
> unmounted it and it was marked clean.
>
> - I then ran fsck.etx3 -f on it and it did not find any problem.
>
> - After increasing size of its LVM volume by
2013 Aug 30
0
Re: 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
2014 Apr 18
0
Many orphaned inodes after resize2fs
Hello,
yesterday I experienced following problem with my ext3 filesystem:
- I had ext3 filesystem of the size of a few TB with journal. I correctly
unmounted it and it was marked clean.
- I then ran fsck.etx3 -f on it and it did not find any problem.
- After increasing size of its LVM volume by 1.5 TB I resized the
filesystem by resize2fs lvm_volume and it finished without problem.
- But
2014 Apr 18
2
Many orphaned inodes after resize2fs
Hello,
yesterday I experienced following problem with my ext3 filesystem:
- I had ext3 filesystem of the size of a few TB with journal. I correctly
unmounted it and it was marked clean.
- I then ran fsck.etx3 -f on it and it did not find any problem.
- After increasing size of its LVM volume by 1.5 TB I resized the
filesystem by resize2fs lvm_volume and it finished without problem.
- But
2003 Feb 09
1
ML9.0:file system completely crashed ext3,"could not find mime type",kde3.0.3
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
2005 Mar 14
0
ext3 filesystem corrupt. Which files are affected?
Hi!
I am using a 377GB ext3-filesystem with evms, spanned over two disks. This
filesystem has worked for more than two years without any problems, it
stores around 30.000 images with sizes between 50kb and 200mb.
Recently, I noticed that images started to disappear. A fsck.ext3 (which
I've unfortunately never run before) revealed a lot of problems, which I
repaired. A log is attached.
Ext3
2014 Apr 18
3
Re: Many orphaned inodes after resize2fs
Hi,
it seems you got it right! I don't know if you read email I sent you before
posting to the mailing list, but I accidentally diagnosed the cause... :)
I've noticed that inodes fsck warned me about, at least ones that I
checked, all have all four timestamps latest in 2010...
The filesystem has maximum 1281998848 inodes, which is timestamp in august
2010. I don't know how it got
2013 Aug 30
2
Strange fsck.ext3 behavior - infinite loop
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
2002 Dec 15
0
[patch] ext3 use-after-free bugfix
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
2003 Feb 04
0
[PATCH] Fix signed use of i_blocks in ext3 truncate
Fix "h_buffer_credits<0" assert failure during truncate.
The bug occurs when the "i_blocks" count in the file's inode overflows
past 2^31. That works fine most of the time, because i_blocks is an
unsigned long, and should go up to 2^32; but there's a place in truncate
where ext3 calculates the size of the next transaction chunk for the
delete, and that mistakenly
2002 Mar 18
0
reproducible ext3 corruption with sync option, 2.4.17, images available
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
2001 Jul 07
2
broken ext3 fs after "poweroff" ext3 0.0.7a/2.2.19 wip 1.21
Hi,
after my X froze i had a fs inconsistency after the journal replay
[...]
EXT3-fs: 03:06: 1 orphan inode deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 64k freed
INIT: version 2.78 booting
Loading /etc/console-tools/default.kmap.gz
Activating swap...
Adding Swap: 264560k
2006 Sep 26
3
EXT3-fs: invalid journal inode.
Hi Everyone,
I have a server which has a raid array on /dev/sdb. After a crash I
tried to mount the array and it failed with:
mount: wrong fs type, bad option, bad superblock on /dev/sdb,
missing codepage or other error
dmesg reports:
EXT3-fs: invalid journal inode.
I tried to run e2fsck and it failed (The output can be seen below).
If anyone has any suggestions on how I can restore
2001 Sep 24
4
part of files in another file after crash
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
because of strange reasons my notebook sometimes crashes short after startup
(but that's not ext3's fault, maybe mem?, when i wait several minutes it
works without problems)
the problem is that after 3 crashes at startup, when my notebook finally
worked i got the msg:
Sep 23 23:29:17 blackbox kernel: EXT3-fs warning (device ide0(3,3)):
2003 Mar 06
0
Re: re problems with ext3 well if think it is
Simon May <simon@imsl.es> wrote:
> We use kernel 2.4.18 with a slackware linux dist.
> e2fsprogs version 1.29
>
> you will see that sendmail was the application that lead to the error
> at the time the machine was doing a weekly new letter to clients
> which puts it under abit of load but not a lot really
> the machine has a 1 Gb processor and 768 Mb RAM so is
2006 Dec 01
1
maintain 6TB filesystem + fsck
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
2003 Dec 04
4
ext3_get_inode_loc: bad inode number:
I've got an approximately 100GB ext3 FS which we recently sized down
from 300GB using e2fsadm (with the disc offline obviously). I noticed the
following in dmesg the other day:
EXT3-fs error (device lvm(58,8)): ext3_get_inode_loc: bad inode number:
14827639
EXT3-fs error (device lvm(58,8)): ext3_get_inode_loc: bad inode number:
14041793
EXT3-fs error (device lvm(58,8)): ext3_get_inode_loc:
2002 Dec 01
3
data corrupting bug in 2.4.20 ext3, data=journal
In 2.4.20-pre5 an optimisation was made to the ext3 fsync function
which can very easily cause file data corruption at unmount time. This
was first reported by Nick Piggin on November 29th (one day after 2.4.20 was
released, and three months after the bug was merged. Unfortunate timing)
This only affects filesystems which were mounted with the `data=journal'
option. Or files which are
2002 Oct 01
0
est3-fs: corrupted, no mount and no fsck worked
Hi, folks
A black out corrupted my file system (ext3, RH7.1). When I boot, the
following message shows up:
hdb: Quantum Fireball CR4.3A, ATA Disk Drive
EXT3-fs error (device ide0 (3,66)): ext3_get_inode_loc: group >= groups
count
EXT3-fs: invalid journal inode
EXT2-fs error (devide ide0 (3,66)): ext2_read_inode: group >= groups count
EXT2-fs: corrupt root inode, run e2fsck
Kernel Panic: