| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: xfs_freeze -f misbehaving under lenny / xfsprogs 2.9.8 |
| From: | Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx> |
| Date: | Tue, 31 Mar 2009 14:34:56 +0200 |
| In-reply-to: | <49D0D01A.8090608@xxxxxxxxxxxxxxxxxx> |
| Organization: | it-management http://it-management.at |
| References: | <49D09F2C.8060406@xxxxxxxxxxxxxxxxxx> <49D0CCEB.1000404@xxxxxxxxxxx> <49D0D01A.8090608@xxxxxxxxxxxxxxxxxx> |
| User-agent: | KMail/1.10.3 (Linux/2.6.28.9-ZMI; KDE/4.1.3; x86_64; ; ) |
On Montag 30 März 2009 Stuart Rowan wrote: > OOI when implementing the freeze ioctl, what made the developers > decide that a freeze can't succeed on an already frozen filesystem > ... you'd expect it to just be a no-op really? So you would break the unfreeze: xfs_freeze -f lvcreate -s (lvcreate does freeze;work;unfreeze) *now you are unfrozen* xfs_freeze -u The problem would be if you expect to be frozen still after the lvcreate command and do some processing, that might be bad. mfg zmi -- // Michael Monnerie, Ing.BSc ----- http://it-management.at // Tel: 0660 / 415 65 31 .network.your.ideas. // PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import" // Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4 // Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [XFS updates] XFS development tree branch, master, updated. v2.6.28-rc3-20838-g5123bc3, Christoph Hellwig |
|---|---|
| Next by Date: | Re: [XFS updates] XFS development tree branch, master, updated. v2.6.28-rc3-20838-g5123bc3, Felix Blyakher |
| Previous by Thread: | Re: xfs_freeze -f misbehaving under lenny / xfsprogs 2.9.8, Eric Sandeen |
| Next by Thread: | Re: Regression? 2.6.27-rc3 segfault on cold boot; not on warm boot., Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |