Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+00\/19\s+v5\]\s+Fix\s+filesystem\s+freezing\s+deadlocks\s*$/: 8 ]

Total 8 documents matching your query.

1. [PATCH 00/19 v5] Fix filesystem freezing deadlocks (score: 1)
Author: Jan Kara <jack@xxxxxxx>
Date: Mon, 16 Apr 2012 18:13:38 +0200
Hello, here is the fifth iteration of my patches to improve filesystem freezing. No serious changes since last time. Mostly I rebased patches and merged this series with series moving file_update_tim
/archives/xfs/2012-04/msg00825.html (12,671 bytes)

2. Re: [PATCH 00/19 v5] Fix filesystem freezing deadlocks (score: 1)
Author: Jan Kara <jack@xxxxxxx>
Date: Mon, 16 Apr 2012 18:16:20 +0200
The subject should have been [PATCH 00/27]... Sorry for the mistake. Honza -- Jan Kara <jack@xxxxxxx> SUSE Labs, CR
/archives/xfs/2012-04/msg00827.html (14,417 bytes)

3. Re: [PATCH 00/19 v5] Fix filesystem freezing deadlocks (score: 1)
Author: Andreas Dilger <adilger@xxxxxxxxxxxxx>
Date: Mon, 16 Apr 2012 15:02:50 -0700
Looking at a desktop system, I think it is very typical that there are open-unlinked files present, so I don't know if this is really an acceptable solution. It isn't clear from your comments whether
/archives/xfs/2012-04/msg00835.html (11,077 bytes)

4. Re: [PATCH 00/19 v5] Fix filesystem freezing deadlocks (score: 1)
Author: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Tue, 17 Apr 2012 10:43:29 +1000
Unlinked-but-open files are the reason that XFS dirties the log after the freeze process is complete. This ensures that if the system crashes while the filesystem is frozen then log recovery during t
/archives/xfs/2012-04/msg00841.html (12,988 bytes)

5. Re: [PATCH 00/19 v5] Fix filesystem freezing deadlocks (score: 1)
Author: Andreas Dilger <adilger@xxxxxxxxxxxxx>
Date: Mon, 16 Apr 2012 22:10:50 -0700
The ext3/4 code has long been able to handle open-unlinked files properly after a crash (they are put into a singly-linked list from the superblock on disk that is processed after journal recovery).
/archives/xfs/2012-04/msg00844.html (13,656 bytes)

6. Re: [PATCH 00/19 v5] Fix filesystem freezing deadlocks (score: 1)
Author: Jan Kara <jack@xxxxxxx>
Date: Tue, 17 Apr 2012 11:32:46 +0200
Thanks for looking at this. It is currently a blanket refusal. And I agree it's problematic. There are two problems with open but unlinked files. One is that some old filesystems cannot get in a cons
/archives/xfs/2012-04/msg00854.html (13,494 bytes)

7. Re: [PATCH 00/19 v5] Fix filesystem freezing deadlocks (score: 1)
Author: Joel Becker <jlbec@xxxxxxxxxxxx>
Date: Tue, 17 Apr 2012 12:34:42 -0700
Let me add my name to the chorus of "we have to handle freezing with open+unlinked, we cannot assume they don't exist." Others have pointed out that we can flag the safe filesystems. I'd even be will
/archives/xfs/2012-04/msg00860.html (17,940 bytes)

8. Re: [PATCH 00/19 v5] Fix filesystem freezing deadlocks (score: 1)
Author: Chris Samuel <chris@xxxxxxxxxxx>
Date: Wed, 18 Apr 2012 10:46:55 +1000
It would also affect current KDE desktops as they tend to use MySQL for Akonadi & Nepomuk, plus anyone using Chromium (and presumably Chrome): samuel@eris:/tmp$ sudo lsof | grep deleted | awk '{print
/archives/xfs/2012-04/msg00864.html (11,908 bytes)


This search system is powered by Namazu