Re: [PATCH 2.6.19 5/5] fs: freeze_bdev with semaphore not mutex
- From: Pavel Machek <pavel@xxxxxx>
- Date: Wed, 15 Nov 2006 21:23:48 +0100
Hi!
There's one more thing, actually. If the on-disk data and metadata are
changed _after_ the sync we do and _before_ we create the snapshot image,
and the subsequent resume fails,
Well, but this is equivalent to a power failure immediately after the sync, so
there _must_ be a way to recover the filesystem from that, no?
Exactly.
I think I'll prepare a patch for freezing the work queues and we'll see what
to do next.
Thanks!
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH 2.6.19 5/5] fs: freeze_bdev with semaphore not mutex
- From: Rafael J. Wysocki
- Re: [PATCH 2.6.19 5/5] fs: freeze_bdev with semaphore not mutex
- References:
- [PATCH 2.6.19 5/5] fs: freeze_bdev with semaphore not mutex
- From: Alasdair G Kergon
- Re: [PATCH 2.6.19 5/5] fs: freeze_bdev with semaphore not mutex
- From: Pavel Machek
- Re: [PATCH 2.6.19 5/5] fs: freeze_bdev with semaphore not mutex
- From: Rafael J. Wysocki
- Re: [PATCH 2.6.19 5/5] fs: freeze_bdev with semaphore not mutex
- From: Rafael J. Wysocki
- [PATCH 2.6.19 5/5] fs: freeze_bdev with semaphore not mutex
- Prev by Date: sexuaally expllicit:aphrodisiacal in bukkkake actionn.
- Next by Date: Re: [patch] floppy: suspend/resume fix
- Previous by thread: Re: [PATCH 2.6.19 5/5] fs: freeze_bdev with semaphore not mutex
- Next by thread: Re: [PATCH 2.6.19 5/5] fs: freeze_bdev with semaphore not mutex
- Index(es):
Relevant Pages
|