| To: | Kristina Clair <kclair@xxxxxxxxx> |
|---|---|
| Subject: | Re: problems with xfs 2.6.13 on gentoo |
| From: | Sonny Rao <sonny@xxxxxxxxxxx> |
| Date: | Thu, 13 Jan 2005 12:16:06 -0500 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <dff375270501060745320f5dc6@mail.gmail.com> |
| References: | <dff375270501060710bc31701@mail.gmail.com> <20050106153535.GA19574@infradead.org> <dff375270501060745320f5dc6@mail.gmail.com> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.2.1i |
On Thu, Jan 06, 2005 at 10:45:46AM -0500, Kristina Clair wrote: > On Thu, 6 Jan 2005 15:35:35 +0000, Christoph Hellwig <hch@xxxxxxxxxxxxx> > wrote: > > On Thu, Jan 06, 2005 at 10:10:24AM -0500, Kristina Clair wrote: > > > xfs_freeze - causes the disk to become completely inaccessible and the > > > machine to lock up. > > > > you did an xfs_freeze -u after you did your snapshot, no? Else this > > is expected behaviour. > > > > It is the initial xfs_freeze -f that locks up the machine... Not trying to insult your intelligence here, but are you running xfs_freeze on your root filesystem? I've done this before and seen exactly what you are describing. Sonny |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | TAKE 923092 - hash table size tweak, Nathan Scott |
|---|---|
| Next by Date: | xfs documentation, Meli Marco |
| Previous by Thread: | Re: problems with xfs 2.6.13 on gentoo, Kristina Clair |
| Next by Thread: | [Bug 378] xfs does not set inode ctime if ATTR_CTIME flag is enabled, bugzilla-daemon |
| Indexes: | [Date] [Thread] [Top] [All Lists] |