Bug#1049873: closing 1049873

2025-02-13 Thread Salvatore Bonaccorso
On Fri, Feb 14, 2025 at 01:13:52AM +0100, Christoph Anton Mitterer wrote: > On Wed, 2025-02-12 at 08:50 +0100, Salvatore Bonaccorso wrote: > > Yes my undsetstanding from your comments was that 6.12.13-1 does not > > expose the problem. > > Okay... let me summarise :-) > > - 6.12. doesn't show t

Bug#1049873: closing 1049873

2025-02-13 Thread Christoph Anton Mitterer
On Wed, 2025-02-12 at 08:50 +0100, Salvatore Bonaccorso wrote: > Yes my undsetstanding from your comments was that 6.12.13-1 does not > expose the problem. Okay... let me summarise :-) - 6.12. doesn't show the original problem (hanging mv) described in this bug I briefly (and wrongly) thought

Bug#1049873: closing 1049873

2025-02-11 Thread Salvatore Bonaccorso
Hi, On Tue, Feb 11, 2025 at 10:52:21PM +0100, Christoph Anton Mitterer wrote: > Hey. > > I think you misunderstood me: > > Only the part where I thought that dCache showed the old size (after > the move has happened, without hanging, when using a current kernel) is > a non-issue. > > The proble

Bug#1049873: closing 1049873

2025-02-11 Thread Christoph Anton Mitterer
Hey. I think you misunderstood me: Only the part where I thought that dCache showed the old size (after the move has happened, without hanging, when using a current kernel) is a non-issue. The problem in 6.1.x, that mv hangs *is* still happening. Cheers, Chris.