Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*XFS\s+filesystem\s+corrupts\s+on\s+umount\s*$/: 22 ]

Total 22 documents matching your query.

1. XFS filesystem corrupts on umount (score: 1)
Author: Russel Ingram <ringram@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 9 Oct 2000 12:00:58 -0600 (MDT)
I have seen umount related things in the archives but nothing that seems to match what I am experiencing here. I just installed the kernel and xfs utils that come on the ProPack 1.4 CD. I created an
/archives/xfs/2000-10/msg00109.html (8,731 bytes)

2. Re: XFS filesystem corrupts on umount (score: 1)
Author: Russell Cattelan <cattelan@xxxxxxxxxxx>
Date: Mon, 09 Oct 2000 13:21:51 -0500
Hmm as long a the FS was cleanly un-mounted this should be occurring. Run the theca command after un-mounting the file system. xfs_logprint -t /dev/ide/host0/bus0/target0/lun0/part4 send us the outpu
/archives/xfs/2000-10/msg00111.html (9,456 bytes)

3. Re: XFS filesystem corrupts on umount (score: 1)
Author: Steve Lord <lord@xxxxxxx>
Date: Mon, 09 Oct 2000 13:59:58 -0500
Hmm, I was not aware ProPack 1.4 was actually released yet, you probably have a beta version. We have at least one case of someone using a copy of ProPack which predated the XFS beta. Could you plea
/archives/xfs/2000-10/msg00115.html (10,001 bytes)

4. Re: XFS filesystem corrupts on umount (score: 1)
Author: Steve Lord <lord@xxxxxxx>
Date: Mon, 09 Oct 2000 14:32:44 -0500
ve k s OK, just checking, in that case looks like you have the correct code.... Steve
/archives/xfs/2000-10/msg00118.html (10,108 bytes)

5. Re: XFS filesystem corrupts on umount (score: 1)
Author: Russell Cattelan <cattelan@xxxxxxxxxxx>
Date: Mon, 09 Oct 2000 16:26:58 -0500
Ok good. at least the log is indicating a clean unmount. Guess we have to track down what else is going wrong. BTW do you have "kio" turned on in the mount options? (that option isn't supported on id
/archives/xfs/2000-10/msg00119.html (9,521 bytes)

6. Re: XFS filesystem corrupts on umount (score: 1)
Author: Daniel Moore <dxm@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 10 Oct 2000 08:38:14 +1100
=> Ok good. => at least the log is indicating a clean unmount. Also note that mount always gives the same 'wrong fs type, bad option, bad superblock' message when the mount fails (for whatever reason
/archives/xfs/2000-10/msg00120.html (9,390 bytes)

7. Re: XFS filesystem corrupts on umount (score: 1)
Author: Steve Lord <lord@xxxxxxx>
Date: Tue, 10 Oct 2000 17:04:39 -0500
The one thing missing from this info is any console messages generated by the failing mount. A successful XFS mount comes out with something like this: Start mounting filesystem: sd(8,4) Starting XFS
/archives/xfs/2000-10/msg00136.html (13,431 bytes)

8. Re: XFS filesystem corrupts on umount (score: 1)
Author: Daniel Moore <dxm@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 11 Oct 2000 09:12:55 +1100
=> > You'll get a better idea of what really happened by checking the messages => > printed to the console or syslog when the mount failed. => Here are the messages from the time I umounted the fs to
/archives/xfs/2000-10/msg00138.html (10,260 bytes)

9. Re: XFS filesystem corrupts on umount (score: 1)
Author: Steve Lord <lord@xxxxxxx>
Date: Tue, 10 Oct 2000 17:39:14 -0500
486 running an Evergreen 100MHz processor with 32M RAM. Funny, I have a guy in my office right now who is trying to kill a system with only 32 Mbytes of ram and cannot make it happen - this is using
/archives/xfs/2000-10/msg00143.html (9,391 bytes)

10. Re: XFS filesystem corrupts on umount (score: 1)
Author: Daniel Moore <dxm@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 11 Oct 2000 09:40:16 +1100
=> This had also occured to me but I had nothing to base it on. The system is => a 486 running an Evergreen 100MHz processor with 32M RAM. You and I must be the only two people who still have only 32
/archives/xfs/2000-10/msg00145.html (9,233 bytes)

11. Re: XFS filesystem corrupts on umount (score: 1)
Author: Daniel Moore <dxm@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 11 Oct 2000 09:48:06 +1100
=> Funny, I have a guy in my office right now who is trying to kill a system w => ith => only 32 Mbytes of ram and cannot make it happen - this is using the test cv => s => tree though. Daniel, maybe
/archives/xfs/2000-10/msg00146.html (9,051 bytes)

12. XFS filesystem corrupts on umount (score: 1)
Author: Russel Ingram <ringram@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 9 Oct 2000 12:00:58 -0600 (MDT)
I have seen umount related things in the archives but nothing that seems to match what I am experiencing here. I just installed the kernel and xfs utils that come on the ProPack 1.4 CD. I created an
/archives/xfs/2000-10/msg00329.html (8,731 bytes)

13. Re: XFS filesystem corrupts on umount (score: 1)
Author: Russell Cattelan <cattelan@xxxxxxxxxxx>
Date: Mon, 09 Oct 2000 13:21:51 -0500
Hmm as long a the FS was cleanly un-mounted this should be occurring. Run the theca command after un-mounting the file system. xfs_logprint -t /dev/ide/host0/bus0/target0/lun0/part4 send us the outpu
/archives/xfs/2000-10/msg00331.html (9,456 bytes)

14. Re: XFS filesystem corrupts on umount (score: 1)
Author: Steve Lord <lord@xxxxxxx>
Date: Mon, 09 Oct 2000 13:59:58 -0500
Hmm, I was not aware ProPack 1.4 was actually released yet, you probably have a beta version. We have at least one case of someone using a copy of ProPack which predated the XFS beta. Could you plea
/archives/xfs/2000-10/msg00335.html (10,001 bytes)

15. Re: XFS filesystem corrupts on umount (score: 1)
Author: Steve Lord <lord@xxxxxxx>
Date: Mon, 09 Oct 2000 14:32:44 -0500
ve k s OK, just checking, in that case looks like you have the correct code.... Steve
/archives/xfs/2000-10/msg00338.html (10,108 bytes)

16. Re: XFS filesystem corrupts on umount (score: 1)
Author: Russell Cattelan <cattelan@xxxxxxxxxxx>
Date: Mon, 09 Oct 2000 16:26:58 -0500
Ok good. at least the log is indicating a clean unmount. Guess we have to track down what else is going wrong. BTW do you have "kio" turned on in the mount options? (that option isn't supported on id
/archives/xfs/2000-10/msg00339.html (9,521 bytes)

17. Re: XFS filesystem corrupts on umount (score: 1)
Author: Daniel Moore <dxm@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 10 Oct 2000 08:38:14 +1100
=> Ok good. => at least the log is indicating a clean unmount. Also note that mount always gives the same 'wrong fs type, bad option, bad superblock' message when the mount fails (for whatever reason
/archives/xfs/2000-10/msg00340.html (9,390 bytes)

18. Re: XFS filesystem corrupts on umount (score: 1)
Author: Steve Lord <lord@xxxxxxx>
Date: Tue, 10 Oct 2000 17:04:39 -0500
The one thing missing from this info is any console messages generated by the failing mount. A successful XFS mount comes out with something like this: Start mounting filesystem: sd(8,4) Starting XFS
/archives/xfs/2000-10/msg00356.html (13,431 bytes)

19. Re: XFS filesystem corrupts on umount (score: 1)
Author: Daniel Moore <dxm@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 11 Oct 2000 09:12:55 +1100
=> > You'll get a better idea of what really happened by checking the messages => > printed to the console or syslog when the mount failed. => Here are the messages from the time I umounted the fs to
/archives/xfs/2000-10/msg00358.html (10,260 bytes)

20. Re: XFS filesystem corrupts on umount (score: 1)
Author: Steve Lord <lord@xxxxxxx>
Date: Tue, 10 Oct 2000 17:39:14 -0500
486 running an Evergreen 100MHz processor with 32M RAM. Funny, I have a guy in my office right now who is trying to kill a system with only 32 Mbytes of ram and cannot make it happen - this is using
/archives/xfs/2000-10/msg00363.html (9,391 bytes)


This search system is powered by Namazu