Displaying 5 results from an estimated 5 matches for "ocfs2_clear_inode".
2010 Aug 20
0
[PATCH] ocfs2: Don't delete orphaned files if we are in the process of umount.
...RT))
queue_work(ocfs2_wq, &osb->dentry_lock_work);
dl->dl_next = osb->dentry_lock_list;
osb->dentry_lock_list = dl;
diff --git a/fs/ocfs2/inode.c b/fs/ocfs2/inode.c
index 0492464..71b47c9 100644
--- a/fs/ocfs2/inode.c
+++ b/fs/ocfs2/inode.c
@@ -1182,12 +1182,32 @@ static void ocfs2_clear_inode(struct inode *inode)
void ocfs2_evict_inode(struct inode *inode)
{
+ int delete = 0;
+
if (!inode->i_nlink ||
(OCFS2_I(inode)->ip_flags & OCFS2_INODE_MAYBE_ORPHANED)) {
+ /*
+ * In case we are in umount and we are now in the
+ * orphan dir, it is safe for us to just clear...
2009 Jan 12
1
Bug in inode deletion code leading to stale inodes
Hello,
I've hit a bug in OCFS2 delete code which results in inodes being left on
disk without any links to them. The workload triggering this creates
directories on one node and deletes them on another node in the cluster.
The inode is not deleted because both nodes bail out from
ocfs2_delete_inode() with:
Skipping delete of 100405 because it is in use on other nodes
The scenario which I
2023 May 04
1
[PATCH 2/2] ocfs2: add error handling path when jbd2 enter ABORT status
...it_cache
+ ... ...
reset: //goto label
+ ocfs2_inc_trans_id(journal); //<1.1>
+ atomic_set(&journal->j_num_trans, 0); //<2>
+ ocfs2_wake_downconvert_thread(osb); //<3>
+ wake_up(&journal->j_checkpointed); //<1.2>
1> trigger hanging
umount
... ...
ocfs2_clear_inode
ocfs2_checkpoint_inode(inode)
+ ocfs2_ci_fully_checkpointed() //1.1: check '->j_trans_id'
+ wait_event(osb->journal->j_checkpointed, ...)
+ 1.2: will wait forever, if commit thread exits.
2> trigger BUG_ON()
ocfs2_journal_shutdown
+ BUG_ON(atomic_read(&(...
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
2008 Sep 04
4
[PATCH 0/3] ocfs2: Switch over to JBD2.
ocfs2 currently uses the Journaled Block Device (JBD) for its
journaling. This is a very stable and tested codebase. However, JBD
is limited by architecture to 32bit block numbers. This means an ocfs2
filesystem is limited to 2^32 blocks. With a 4K blocksize, that's 16TB.
People want larger volumes.
Fortunately, there is now JBD2. JBD2 adds 64bit block number support
and some other