| To: | Steve Lord <lord@xxxxxxx> |
|---|---|
| Subject: | Re: 2.6.0-test5-mm3 & XFS FS Corruption (or not?) |
| From: | Walt H <waltabbyh@xxxxxxxxxxx> |
| Date: | Sun, 21 Sep 2003 18:01:06 -0700 |
| Cc: | Linux Kernel <linux-kernel@xxxxxxxxxxxxxxx>, Linux XFS Mailing List <linux-xfs@xxxxxxxxxxx> |
| In-reply-to: | <1064173697.2285.4.camel@laptop.americas.sgi.com> |
| References: | <3F6DC819.8060003@comcast.net> <3F6DE929.4040904@comcast.net> <1064173697.2285.4.camel@laptop.americas.sgi.com> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030914 |
Steve Lord wrote: > > If I am correct, test5-mm3 contains a bad version of the xfs code, there > was a bug where the i_flags field was setup from an uninitialized stack > variable. mm3 came out during the two days this was in Linus's tree. > I had some very odd behavior with this code base, rm -r -f would try and > cd into files and other bizzare things, files could appear to be > immutable or append only or things they were not. This sounds like > similar behavior you that you saw. It is fixed in the latest code Linus > has. > > Steve Thanks for the reply Steve. I'm guessing that this code hasn't hit CVS yet, as I can still reproduce it with a current CVS @ 9/21/03 ~ 17:30 PST Sounds like this is a known issue, so I'll just go back to the xfs code from -mm2 for now. -Walt |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: 2.6.0-test5-mm3 & XFS FS Corruption (or not?), Steve Lord |
|---|---|
| Next by Date: | Re: 2.6.0-test5-mm3 & XFS FS Corruption (or not?), Nathan Scott |
| Previous by Thread: | Re: 2.6.0-test5-mm3 & XFS FS Corruption (or not?), Steve Lord |
| Next by Thread: | Re: 2.6.0-test5-mm3 & XFS FS Corruption (or not?), Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |