search for: end_tran

...ost, you posted the output from the join command, the relevant parts were these: Your error started here: An operation failed during a batch mode transaction, the transaction was rolled back DSDB Transaction [commit] at [Thu, 05 Dec 2024 19:29:47.054187 EET] duration [24679161] status [1] reason [end_trans error on DC=SUB,DC=DOM,DC=TLD: An operation failed during a batch mode transaction, the transaction was rolled back] {"timestamp": "2024-12-05T19:29:47.054240+0200", "type": "dsdbTransaction", "dsdbTransaction": {"version": {"major&q...

...ost, you posted the output from the join command, the relevant parts were these: Your error started here: An operation failed during a batch mode transaction, the transaction was rolled back DSDB Transaction [commit] at [Thu, 05 Dec 2024 19:29:47.054187 EET] duration [24679161] status [1] reason [end_trans error on DC=SUB,DC=DOM,DC=TLD: An operation failed during a batch mode transaction, the transaction was rolled back] {"timestamp": "2024-12-05T19:29:47.054240+0200", "type": "dsdbTransaction", "dsdbTransaction": {"version": {"major&q...

While resuming my testing for adding a new DC with higher Samba version I have some questions: 1. do I have to expunge tombstones on each DC or just one (and replication will remove it from others). - I think it should be run on all DCs. 2. same question for dbcheck 3. Rowland mentioned that the error message I get when trying the DC is just a result of the real issue. In which section of the

...ost, you posted the output from the join command, the relevant parts were these: Your error started here: An operation failed during a batch mode transaction, the transaction was rolled back DSDB Transaction [commit] at [Thu, 05 Dec 2024 19:29:47.054187 EET] duration [24679161] status [1] reason [end_trans error on DC=SUB,DC=DOM,DC=TLD: An operation failed during a batch mode transaction, the transaction was rolled back] {"timestamp": "2024-12-05T19:29:47.054240+0200", "type": "dsdbTransaction", "dsdbTransaction": {"version": {"major&q...

...ed(page); set_page_dirty(page); + i_size_write(inode, from); unlock_extent_cached(io_tree, page_start, page_end, &cached_state, GFP_NOFS); @@ -3459,7 +3465,9 @@ static int btrfs_setsize(struct inode *inode, loff_t newsize) ret = btrfs_update_inode(trans, root, inode); btrfs_end_transaction_throttle(trans, root); } else { - + btrfs_wait_ordered_range(inode, + newsize & ~(root->sectorsize - 1), + (u64)-1); /* * We''re truncating a file that used to have good data down to * zero. Make sure it gets into the ordered flush list so that @@ -3469...

...Repacking database from v1 to v2 format (first record CN=FirstName LastName,CN=Users,DC=SUB,DC=DOM,DC=TLD) An operation failed during a batch mode transaction, the transaction was rolled back DSDB Transaction [commit] at [Thu, 05 Dec 2024 19:29:47.054187 EET] duration [24679161] status [1] reason [end_trans error on DC=SUB,DC=DOM,DC=TLD: An operation failed during a batch mode transaction, the transaction was rolled back] {"timestamp": "2024-12-05T19:29:47.054240+0200", "type": "dsdbTransaction", "dsdbTransaction": {"version": {"major&q...

...from v1 to v2 format (first record CN=FirstName > LastName,CN=Users,DC=SUB,DC=DOM,DC=TLD) An operation failed during a > batch mode transaction, the transaction was rolled back DSDB > Transaction [commit] at [Thu, 05 Dec 2024 19:29:47.054187 EET] > duration [24679161] status [1] reason [end_trans error on > DC=SUB,DC=DOM,DC=TLD: An operation failed during a batch mode > transaction, the transaction was rolled back] {"timestamp": > "2024-12-05T19:29:47.054240+0200", "type": "dsdbTransaction", > "dsdbTransaction": {"version&q...

...trans, goto end_no_trans; } - if (root->fs_info->last_trans_log_full_commit > + if (atomic64_read(&root->fs_info->last_trans_log_full_commit) > atomic64_read(&root->fs_info->last_trans_committed)) { ret = 1; goto end_no_trans; @@ -3819,7 +3824,8 @@ end_trans: dput(old_parent); if (ret < 0) { WARN_ON(ret != -ENOSPC); - root->fs_info->last_trans_log_full_commit = trans->transid; + atomic64_set(&root->fs_info->last_trans_log_full_commit, + trans->transid); ret = 1; } btrfs_end_log_trans(root); -- 1.7.11.7...

...rent(struct btrfs_trans_handle *trans, break; if (BTRFS_I(inode)->generation > - root->fs_info->last_trans_committed) { + atomic64_read(&root->fs_info->last_trans_committed)) { ret = btrfs_log_inode(trans, root, inode, inode_only); if (ret) goto end_trans; @@ -4063,9 +4065,9 @@ int btrfs_log_new_name(struct btrfs_trans_handle *trans, * from hasn''t been logged, we don''t need to log it */ if (BTRFS_I(inode)->logged_trans <= - root->fs_info->last_trans_committed && + atomic64_read(&root->fs_...

After running ceph on XFS for some time, I decided to try btrfs again. Performance with the current "for-linux-min" branch and big metadata is much better. The only problem (?) I''m still seeing is a warning that seems to occur from time to time: [87703.784552] ------------[ cut here ]------------ [87703.789759] WARNING: at fs/btrfs/inode.c:2103