Displaying 4 results from an estimated 4 matches for "ocfs2_truncate_for_delet".
Did you mean:
ocfs2_truncate_for_delete
2011 Jan 12
1
Problems with fsck
...ve_extent:5526 ERROR: status = -5
Jan 11 23:11:56 www1 kernel: [ 2339.655531]
(mc,3305,0):ocfs2_remove_btree_range:5717 ERROR: status = -5
Jan 11 23:11:56 www1 kernel: [ 2339.656908]
(mc,3305,0):ocfs2_commit_truncate:7117 ERROR: status = -5
Jan 11 23:11:56 www1 kernel: [ 2339.658152]
(mc,3305,0):ocfs2_truncate_for_delete:622 ERROR: status = -5
Jan 11 23:11:56 www1 kernel: [ 2339.659423]
(mc,3305,0):ocfs2_wipe_inode:793 ERROR: status = -5
Jan 11 23:11:56 www1 kernel: [ 2339.660700]
(mc,3305,0):ocfs2_delete_inode:1085 ERROR: status = -5
Jan 11 23:15:41 www1 kernel: [ 2565.101905] OCFS2: ERROR (device drbd1):
oc...
2009 Feb 03
1
Problem with ordered mode handling on truncate
...rans, inode, ...)
discard data of "inode"
commit "trans"
---- CRASH
The correct fix to this problem is to call
jbd2_journal_begin_ordered_truncate() after inode has been added to orphan
list (new i_size written respectively). That function is called from two
places:
1) ocfs2_truncate_for_delete() - easy to fix, just move the call just after
the write of the inode.
2) ocfs2_setattr() - we can move the call into ocfs2_truncate_file() but
that would mean calling jbd2_journal_begin_ordered_truncate()
and consequently ocfs2_write_page() under ip_alloc_sem - not too nice.
Furthermo...
2010 Jun 14
3
Diagnosing some OCFS2 error messages
...1958 ERROR: status = -5
[94355.116358] (ocfs2_wq,5995,6):ocfs2_find_new_last_ext_blk:6655
ERROR: status = -5
[94355.116361] (ocfs2_wq,5995,6):ocfs2_do_truncate:6900 ERROR: status = -5
[94355.116364] (ocfs2_wq,5995,6):ocfs2_commit_truncate:7559 ERROR: status = -5
[94355.116370] (ocfs2_wq,5995,6):ocfs2_truncate_for_delete:597 ERROR:
status = -5
[94355.116373] (ocfs2_wq,5995,6):ocfs2_wipe_inode:770 ERROR: status = -5
[94355.116376] (ocfs2_wq,5995,6):ocfs2_delete_inode:1062 ERROR: status = -5
...although the particular extent block number varies somewhat.
In addition, when I run "fsck.ocfs2 -y -f /dev/md0&q...
2009 Feb 13
44
[PATCH 0/40] ocfs2: Detach ocfs2 metadata I/O from struct inode
The following series of patches attempts to detach metadata I/O from
struct inode. They are currently tied together pretty tightly.
Metadata reads happen via the ocfs2_read_blocks() functions, writes via
both jbd2 and ocfs2_write_blocks().
- Each inode has a cache of associated metadata blocks stored on its
ip_metadata_cache member. The ocfs2_read/write_blocks() functions
take a struct