Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Broken\s+Log\s+Help\s+Needed\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Broken\s+Log\s+Help\s+Needed\s*$/: 21 ]

Total 21 documents matching your query.

1. RE: Broken Log Help Needed (score: 1): Author:; Date: Mon, 27 Oct 2003 15:47:16 -0600; Woops, forgot the xfs_db output and the xfs_info output: <xfs_db> [root@Phoenix root]# xfs_db -r /dev/sdb magicnum = 0x58465342 blocksize = 4096 dblocks = 524288 rblocks = 0 rextents = 0 uuid = c7176; /archives/xfs/2003-10/msg00217.html (8,466 bytes)
2. Broken Log Help Needed (score: 1): Author:; Date: Mon, 27 Oct 2003 15:55:43 -0600; I think the previous one had too big an attachment. Here is a gzipped set of xfs_logprint and xfs_logprint -t -b -i. I would provide a URL, but I don't have one to use ATM. The issue is that I don't; /archives/xfs/2003-10/msg00218.html (8,235 bytes)
3. Re: Broken Log Help Needed (score: 1): Author:; Date: Mon, 27 Oct 2003 18:38:04 -0600 (CST); Can you send the exact oops message.. where it occured, etc? Here's an example: [root@HOSTNAME root]# /a23/overby/bin.l/mkfs.xfs -f -b size=4096 -l size=8192b /dev/hda6 meta-data=/dev/hda6 isize=256; /archives/xfs/2003-10/msg00221.html (8,879 bytes)
4. Re: Broken Log Help Needed (score: 1): Author:; Date: Tue, 28 Oct 2003 15:33:54 -0600; They are on this list somewhere. I've sent several over time. This has been going on for a long while, and is very reproduceable. I'd love for someone work with me on this to get this fixed, I'm sure; /archives/xfs/2003-10/msg00229.html (10,182 bytes)
5. Re: Broken Log Help Needed (score: 1): Author:; Date: Tue, 28 Oct 2003 15:35:53 -0600; Ok. missed this part, I thought it was what I'd typed. I'll do this, though the system is now back into production, I can see about trying to break a log again and then extract it. -- Austin Gonyou <; /archives/xfs/2003-10/msg00230.html (8,760 bytes)
6. Re: Broken Log Help Needed (score: 1): Author:; Date: Tue, 28 Oct 2003 15:51:36 -0600 (CST); er, this was just part of my example. I started with a clean filesystem. You don't have to wipe your filesystem... in fact, if you do that your log will be very clean and you don't need to bother dum; /archives/xfs/2003-10/msg00231.html (9,027 bytes)
7. Re: Broken Log Help Needed (score: 1): Author:; Date: Wed, 29 Oct 2003 13:27:14 -0600; Yes..yes..I know. :) I wasn't going to kill my fs. I was just referring to xfs_repair -L. -- Austin Gonyou <austin@xxxxxxxxxxxxxxx> Coremetrics, Inc.; /archives/xfs/2003-10/msg00239.html (9,583 bytes)
8. RE: Broken Log Help Needed (score: 1): Author: >; Date: Mon, 27 Oct 2003 15:47:16 -0600; Woops, forgot the xfs_db output and the xfs_info output: <xfs_db> [root@Phoenix root]# xfs_db -r /dev/sdb magicnum = 0x58465342 blocksize = 4096 dblocks = 524288 rblocks = 0 rextents = 0 uuid = c7176; /archives/xfs/2003-10/msg00501.html (8,466 bytes)
9. Broken Log Help Needed (score: 1): Author: >; Date: Mon, 27 Oct 2003 15:55:43 -0600; I think the previous one had too big an attachment. Here is a gzipped set of xfs_logprint and xfs_logprint -t -b -i. I would provide a URL, but I don't have one to use ATM. The issue is that I don't; /archives/xfs/2003-10/msg00502.html (8,235 bytes)
10. Re: Broken Log Help Needed (score: 1): Author: >; Date: Mon, 27 Oct 2003 18:38:04 -0600 (CST); Can you send the exact oops message.. where it occured, etc? Here's an example: [root@HOSTNAME root]# /a23/overby/bin.l/mkfs.xfs -f -b size=4096 -l size=8192b /dev/hda6 meta-data=/dev/hda6 isize=256; /archives/xfs/2003-10/msg00505.html (8,879 bytes)
11. Re: Broken Log Help Needed (score: 1): Author: >; Date: Tue, 28 Oct 2003 15:33:54 -0600; They are on this list somewhere. I've sent several over time. This has been going on for a long while, and is very reproduceable. I'd love for someone work with me on this to get this fixed, I'm sure; /archives/xfs/2003-10/msg00513.html (10,182 bytes)
12. Re: Broken Log Help Needed (score: 1): Author: >; Date: Tue, 28 Oct 2003 15:35:53 -0600; Ok. missed this part, I thought it was what I'd typed. I'll do this, though the system is now back into production, I can see about trying to break a log again and then extract it. -- Austin Gonyou <; /archives/xfs/2003-10/msg00514.html (8,760 bytes)
13. Re: Broken Log Help Needed (score: 1): Author: >; Date: Tue, 28 Oct 2003 15:51:36 -0600 (CST); er, this was just part of my example. I started with a clean filesystem. You don't have to wipe your filesystem... in fact, if you do that your log will be very clean and you don't need to bother dum; /archives/xfs/2003-10/msg00515.html (9,027 bytes)
14. Re: Broken Log Help Needed (score: 1): Author: >; Date: Wed, 29 Oct 2003 13:27:14 -0600; Yes..yes..I know. :) I wasn't going to kill my fs. I was just referring to xfs_repair -L. -- Austin Gonyou <austin@xxxxxxxxxxxxxxx> Coremetrics, Inc.; /archives/xfs/2003-10/msg00523.html (9,583 bytes)
15. RE: Broken Log Help Needed (score: 1): Author: Austin Gonyou <austin@xxxxxxxxxxxxxxx>; Date: Mon, 27 Oct 2003 15:47:16 -0600; Woops, forgot the xfs_db output and the xfs_info output: <xfs_db> [root@Phoenix root]# xfs_db -r /dev/sdb magicnum = 0x58465342 blocksize = 4096 dblocks = 524288 rblocks = 0 rextents = 0 uuid = c7176; /archives/xfs/2003-10/msg00785.html (8,466 bytes)
16. Broken Log Help Needed (score: 1): Author: Austin Gonyou <austin@xxxxxxxxxxxxxxx>; Date: Mon, 27 Oct 2003 15:55:43 -0600; I think the previous one had too big an attachment. Here is a gzipped set of xfs_logprint and xfs_logprint -t -b -i. I would provide a URL, but I don't have one to use ATM. The issue is that I don't; /archives/xfs/2003-10/msg00786.html (8,235 bytes)
17. Re: Broken Log Help Needed (score: 1): Author: Glen Overby <overby@xxxxxxx>; Date: Mon, 27 Oct 2003 18:38:04 -0600 (CST); Can you send the exact oops message.. where it occured, etc? Here's an example: [root@HOSTNAME root]# /a23/overby/bin.l/mkfs.xfs -f -b size=4096 -l size=8192b /dev/hda6 meta-data=/dev/hda6 isize=256; /archives/xfs/2003-10/msg00789.html (8,912 bytes)
18. Re: Broken Log Help Needed (score: 1): Author: Austin Gonyou <austin@xxxxxxxxxxxxxxx>; Date: Tue, 28 Oct 2003 15:33:54 -0600; They are on this list somewhere. I've sent several over time. This has been going on for a long while, and is very reproduceable. I'd love for someone work with me on this to get this fixed, I'm sure; /archives/xfs/2003-10/msg00797.html (10,252 bytes)
19. Re: Broken Log Help Needed (score: 1): Author: Austin Gonyou <austin@xxxxxxxxxxxxxxx>; Date: Tue, 28 Oct 2003 15:35:53 -0600; Ok. missed this part, I thought it was what I'd typed. I'll do this, though the system is now back into production, I can see about trying to break a log again and then extract it. -- Austin Gonyou <; /archives/xfs/2003-10/msg00798.html (8,830 bytes)
20. Re: Broken Log Help Needed (score: 1): Author: Glen Overby <overby@xxxxxxx>; Date: Tue, 28 Oct 2003 15:51:36 -0600 (CST); er, this was just part of my example. I started with a clean filesystem. You don't have to wipe your filesystem... in fact, if you do that your log will be very clean and you don't need to bother dum; /archives/xfs/2003-10/msg00799.html (9,095 bytes)

Current List: 1 - 20
Page: [1] [2]