Displaying 4 results from an estimated 4 matches for "ext3_mkdir".
2005 Aug 05
2
FS problems on Centos4 LVM
...ting filesystem read-only
Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4) in
ext3_reserve_inode_write: Journal has aborted
Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4) in
start_transaction: Journal has aborted
Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4) in
ext3_mkdir: Journal has aborted
What is going on? How do I fix it?
Regards,
Jim
The favour of a direct response is requested as I am a diges
subscriber.
--
*** e-mail is NOT a secure channel ***
James B. Byrne mailto:ByrneJB.<token>@Harte-Lyne.ca
Harte & Lyne Limited...
2005 Dec 01
0
Errors reported by Coverity in ext3.
...cases. The
places where the return value is not checked are(in the current
kernel version):
fs/ext3/inode.c ext3_clear_blocks 1829
fs/ext3/namei.c ext3_append 63
fs/ext3/namei.c ext3_delete_entry 1585
fs/ext3/namei.c ext3_mkdir 1745
fs/ext3/namei.c ext3_rename 2273
fs/ext3/namei.c ext3_rename 2328
I have attached the full text of errors reported by Coverity on
kernel version 2.6.13, for reference.
---
1. Error reported in ext3/namei.c
---
CID: 3549...
2001 Dec 06
1
2.2.19: Assertion failure in ext3_new_block() at balloc.c line 709
...prt+2a1f/a240>
Trace; c01f3220 <cprt+2c40/a240>
Trace; c0149314 <ext3_alloc_block+30/38>
Trace; c0149636 <inode_getblk+d2/20c>
Trace; c0148bbf <ext3_new_inode+6ef/7ac>
Trace; c0149b27 <ext3_getblk+c7/244>
Trace; c0149ccc <ext3_bread+28/118>
Trace; c014bb4b <ext3_mkdir+117/634>
Trace; c012ee8f <lookup_dentry+15f/1e8>
Trace; c012f57d <sys_mkdir+e1/11c>
Trace; c010a06c <system_call+34/38>
Trace; c010002b <startup_32+2b/11e>
Code; c0146885 <ext3_new_block+635/738>
00000000 <_EIP>:
Code; c0146885 <ext3_new_block+635/738>...
2003 Aug 02
7
[2.6] Perl weirdness with ext3 and HTREE
Hi
I have mailed about this previously, but back then it was not
really confirmed, so I have let it be at that.
Anyhow, problem is that for some reason 2.5/2.6 ext3 with HTREE
support do not like what perl-5.8.0 does during installation.
It *seems* like one of the temporary files created during manpage
installation do not get unlinked properly, or gets into the
hash (this possible?) and cause