| To: | Chris Wedgwood <cw@xxxxxxxx>, linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: raid1 (u)mount error |
| From: | thomas <tom@xxxxxxxx> |
| Date: | Tue, 10 Sep 2002 22:22:03 +0200 |
| In-reply-to: | <20020910195703.GA9987@tapu.f00f.org> |
| References: | <527280437.20020910155814@huno.net> <20020910182241.GA5230@tapu.f00f.org> <1031682497.22845.97.camel@jen.americas.sgi.com> <20020910184228.GA5323@tapu.f00f.org> <1031683668.22845.102.camel@jen.americas.sgi.com> <20020910185723.GA5375@tapu.f00f.org> <1298234671.20020910211407@huno.net> <20020910192023.GA5470@tapu.f00f.org> <1019359078.20020910213251@huno.net> <20020910195703.GA9987@tapu.f00f.org> |
| Reply-to: | thomas <tom@xxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
while i was waiting for the responses i made a fresh 2.4.19-xfs with gcc2.95 just for kicks and guess what the error vanished. now the only difference between this kernel and the older one was the gcc version (3.1.1 vs 2.95.4) and the older one had some crazy CFLAGS, because i tried to optimize it for my VIA C3. i double checked and booted with the old kernel again and the error is back. i did this several times (new>old>new>old>new) just to be extra sure. false alarm, no xfs problem :) thomas |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: raid1 (u)mount error, Chris Wedgwood |
|---|---|
| Next by Date: | TAKE - change symlink perms to 777, Eric Sandeen |
| Previous by Thread: | Re: raid1 (u)mount error, Chris Wedgwood |
| Next by Thread: | Re: raid1 (u)mount error, Chris Wedgwood |
| Indexes: | [Date] [Thread] [Top] [All Lists] |