| To: | linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: Problem with XFS and JFS |
| From: | Ivan Kocher <ikocher@xxxxxxxxxxxxxxxxx> |
| Date: | Wed, 25 Feb 2004 05:25:13 -0600 |
| In-reply-to: | <1077575947.7791.88.camel@stout.americas.sgi.com> |
| Organization: | Fintec SA |
| References: | <403A3366.3070809@odin.fintec.co.cr> <1077557148.4497.1.camel@naboo.americas.sgi.com> <403A790F.7060100@odin.fintec.co.cr> <1077575947.7791.88.camel@stout.americas.sgi.com> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030313 |
By now I can't do that ... I run jfs_fsck on the partition, and that removed the problem... I hope it doesn't bite me again. I will try to reproduce the bug next week, by now I must set this units in production, and can make more test on this matter. I am still wondering what went wrong. I _like_ xfs, is has proven to me that it really delivers, but well under certain conditions I went for jfs ... :(
It does not make sense that xfs would be trying to replay a log from a partition which has been zeroed, then mkfs.jfs'd - there should be no xfs superblock magic left, and xfs should not try to do anything. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS patched RHELv3 kernels now available - please test, Bela Babik |
|---|---|
| Next by Date: | Re: kernel debugger and Infortrend and bad blocks, James Pearson |
| Previous by Thread: | Re: Problem with XFS and JFS, Eric Sandeen |
| Next by Thread: | TAKE 907752 - xfstests v2 log recovery, Tim Shimmin |
| Indexes: | [Date] [Thread] [Top] [All Lists] |