search for: ext3_getblk

Displaying 8 results from an estimated 8 matches for "ext3_getblk".

2003 Dec 10
0
VFS: brelse: Trying to free free buffer
...] bh_lru_install+0x7c/0xb0 Dec 11 04:03:56 fendrian kernel: [__find_get_block+96/160] __find_get_block+0x60/0xa0 Dec 11 04:03:56 fendrian kernel: [__getblk_slow+24/224] __getblk_slow+0x18/0xe0 Dec 11 04:03:56 fendrian kernel: [__getblk+42/48] __getblk+0x2a/0x30 Dec 11 04:03:56 fendrian kernel: [ext3_getblk+123/528] ext3_getblk+0x7b/0x210 Dec 11 04:03:56 fendrian kernel: [submit_bio+61/112] submit_bio+0x3d/0x70 Dec 11 04:03:56 fendrian kernel: [ll_rw_block+88/128] ll_rw_block+0x58/0x80 Dec 11 04:03:56 fendrian kernel: [ext3_find_entry+288/976] ext3_find_entry+0x120/0x3d0 Dec 11 04:03:56 fendrian ke...
2003 Mar 02
1
2.5.59 ext3 error message
...f79>] [<c0155126>] [<c0154f79>] [<c01540c2>] [<c0154244>] [<c0109227>] Trace; c01468f0 <__brelse+35/37> Trace; c0146aa9 <bh_lru_install+b1/ed> Trace; c0146b57 <__find_get_block+72/74> Trace; c0146b84 <__getblk+2b/51> Trace; c0175a17 <ext3_getblk+ab/2f1> Trace; c023cbfa <serio_interrupt+4e/50> Trace; c023d2f1 <i8042_interrupt+f5/1ff> Trace; c0175c90 <ext3_bread+33/a2> Trace; c01728e9 <ext3_readdir+e6/4e0> Trace; c01ad7d6 <__copy_to_user_ll+74/78>
2001 May 02
4
oops 2.2.19 ext3 0.0.6b prune_dcache
...ca2d3280 ca77b8a0 00000246 ffff8890 00000000 cffc0018 c013266b cfffc620 cefd1340 00000010 00000246 00000000 c021ced0 00001004 cd511dac cffd50e0 00001000 00000000 00001004 c021ced0 00001004 Call Trace: [prune_dcache+295/360] [try_to_free_inodes+190/260] [scsi_old_times_out+0/300] [ext3_getblk+198/568] [grow_inodes+32/428] [cprt+14006/37792] [get_new_inode+197/312] [iget4+117/128] [__brelse+29/192] [iget+22/32] [ext3_lookup+90/140] [real_lookup+91/180] [permission+32/56] [lookup_dentry+304/504] [__fput+74/84] [open_namei+105/776] [fput+70/84] [filp_open+74/264] [filp_open+17/264]...
2001 Jul 05
1
2.2.19/0.0.7a assertion failure
...940] [cprt+24767/41940] [read_block_bitmap+65/144] [journal_get_undo_access+45/340] [journal_get_undo_access+29/340] [ext3_new_block+838/1820] [do_get_write_access+1027/1068] [ext3_alloc_block+57/68] [journal_get_write_access+28/124] [journal_get_write_access+113/124] [block_getblk+358/792] [ext3_getblk+554/568] [ext3_file_write+1390/2384] [sys_write+212/260] [error_code+53/64] Linux theirongiant 2.2.19+ext3-0.0.7a #3 Sun Jul 1 15:45:44 EST 2001 i686 unknown And... as I found out when I tried to save the above email, writing to disk eventually wound up with no disk access and no writing on the f...
2001 Apr 29
1
freeing, allocating and free blocks in Ext3
...that the blocks freed by the truncation were not yet available to the write because the transaction had not committed. The total number of blocks write required in addition to what was made unavailable by the truncate transaction exceeded the size of this (admittedly small) ext3 file system. So ext3_getblk bummed out. What does worry me is that the superblock information indicating available blocks is simply incorrect until the truncate transaction has committed. I wonder if we could either change that, or maintain a constant that indicates how many blocks are unavailable until the next commit. I...
2001 Oct 07
2
ext3 and ls in a deletted directory
Hi, With kernel 2.4.10, when I do $ mkdir foo; cd foo; rmdir ../foo; ls then ls becomes zombie. $ ps xau|grep ls liu 596 0.0 0.0 148 88 ? D 12:03 0:00 ls This does not happen with 2.4.10 on an ext2 filesystem, nor with 2.4.9/ext3. The command cd instead of ls is OK. Distribution is Slackware 8.0 and the kernels are stock ones. Liu
2001 Jun 21
0
oops in ext3_new_block / 2.2.19/0.0.7a
...k+557/6c8> <===== Trace; c014ff63 <do_get_write_access+403/42c> Trace; c014574d <ext3_alloc_block+39/44> Trace; c014ffa8 <journal_get_write_access+1c/7c> Trace; c014fffd <journal_get_write_access+71/7c> Trace; c0145d5a <block_getblk+16a/31c> Trace; c0146136 <ext3_getblk+22a/238> Trace; c0143bd2 <ext3_file_write+566/95c> Trace; c01267c0 <sys_write+d4/104> Trace; c010b018 <common_interrupt+18/20> Trace; c010a0b8 <system_call+34/38> Trace; c010002b <startup_32+2b/11d> Code; c0142ba3 <ext3_new_block+557/6c8> 00000000 <_EIP&gt...
2001 Dec 06
1
2.2.19: Assertion failure in ext3_new_block() at balloc.c line 709
...gt;>EIP; c0146885 <ext3_new_block+635/738> <===== Trace; c01f2fff <cprt+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_blo...