Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Errors\s+using\s+amanda\/xfsdump\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Errors\s+using\s+amanda\/xfsdump\s*$/: 20 ]

Total 20 documents matching your query.

1. Re: Errors using amanda/xfsdump (score: 1): Author: Justin Tripp <justin@xxxxxxxxx>; Date: Mon, 7 May 2001 16:07:08 -0600 (MDT); Okay -- I have had a chance to hook up a serial console to my machine and have been able to get it to crash again. The error messages and stack traces are as follows: xfs_iget_core: ambiguous vns: vp; /archives/xfs/2001-05/msg00399.html (14,511 bytes)
2. Re: Errors using amanda/xfsdump (score: 1): Author: Federico Sevilla III <jijo@xxxxxxxxxxxxxxx>; Date: Tue, 8 May 2001 17:42:02 +0800 (PHT); Hi, this is a little late and not particularly XFS-specific but ... 3Ware sent me an e-mail about a problem they found with their Escalade 6400 controllers, RAID 5, and ext2. Their e-mail did not hav; /archives/xfs/2001-05/msg00424.html (13,440 bytes)
3. Re: Errors using amanda/xfsdump (score: 1): Author: Justin Tripp <justin@xxxxxxxxx>; Date: Tue, 8 May 2001 07:35:03 -0600 (MDT); I do not believe this is the problem. For the RAID 5 failure to occur, one must run the raid in degraded mode (e.g. with a disk failed.) My raid has not run in the degraded mode, so according to them; /archives/xfs/2001-05/msg00430.html (16,014 bytes)
4. Re: Errors using amanda/xfsdump (score: 1): Author: Steve Lord <lord@xxxxxxx>; Date: Tue, 08 May 2001 08:41:41 -0500; Justin, you are correct, you have found a scenario which xfs cannot always cope with - in fact there is a deliberate panic in there. This will only be triggered by the combination of NFS and local ac; /archives/xfs/2001-05/msg00431.html (17,543 bytes)
5. Re: Errors using amanda/xfsdump (score: 1): Author: lan@xxxxxxx>; Date: Mon, 7 May 2001 16:07:08 -0600 (MDT); Okay -- I have had a chance to hook up a serial console to my machine and have been able to get it to crash again. The error messages and stack traces are as follows: xfs_iget_core: ambiguous vns: vp; /archives/xfs/2001-05/msg01763.html (14,511 bytes)
6. Re: Errors using amanda/xfsdump (score: 1): Author: xxxxxxxxxxx>; Date: Tue, 8 May 2001 17:42:02 +0800 (PHT); Hi, this is a little late and not particularly XFS-specific but ... 3Ware sent me an e-mail about a problem they found with their Escalade 6400 controllers, RAID 5, and ext2. Their e-mail did not hav; /archives/xfs/2001-05/msg01788.html (13,440 bytes)
7. Re: Errors using amanda/xfsdump (score: 1): Author: een@xxxxxxx>; Date: Tue, 8 May 2001 07:35:03 -0600 (MDT); I do not believe this is the problem. For the RAID 5 failure to occur, one must run the raid in degraded mode (e.g. with a disk failed.) My raid has not run in the degraded mode, so according to them; /archives/xfs/2001-05/msg01794.html (16,014 bytes)
8. Re: Errors using amanda/xfsdump (score: 1): Author: n@xxxxxxxxx>; Date: Tue, 08 May 2001 08:41:41 -0500; Justin, you are correct, you have found a scenario which xfs cannot always cope with - in fact there is a deliberate panic in there. This will only be triggered by the combination of NFS and local ac; /archives/xfs/2001-05/msg01795.html (17,543 bytes)
9. Errors using amanda/xfsdump (score: 1): Author: x>; Date: Wed, 25 Apr 2001 14:22:47 -0600 (MDT); I have been trying to backup xfs partitions using amanda, and there seems to be a problem with xfsdump. Amanda suprisingly recognized xfsdump and seems to tried to do the backup correctly. On the oth; /archives/xfs/2001-04/msg00586.html (8,666 bytes)
10. Re: Errors using amanda/xfsdump (score: 1): Author: x>; Date: Wed, 25 Apr 2001 15:39:19 -0500; Hmm, the xfs process is the x font server, nothing directly to do with xfs itself. However, obviously xfs is at the back of your problem. Can you provide a backtrace from kdb after it drops into the; /archives/xfs/2001-04/msg00587.html (10,358 bytes)
11. Re: Errors using amanda/xfsdump (score: 1): Author: x>; Date: Wed, 25 Apr 2001 14:46:17 -0600 (MDT); I meant to say that the process 803 was xfsdump. Sorry. I had a brain cramp there ... .justin. -- Justin Leonard Tripp justin@xxxxxxxxxx Configurable Computing Laboratory Research Assistant CB 461 x8; /archives/xfs/2001-04/msg00588.html (11,253 bytes)
12. Re: Errors using amanda/xfsdump (score: 1): Author: x>; Date: Thu, 26 Apr 2001 13:19:11 -0500; Having thought about this some more, I think the problem is being caused by the combination of local and remote access to the same files - lookups coming in from both directions in parallel almost in; /archives/xfs/2001-04/msg00605.html (10,296 bytes)
13. Errors using amanda/xfsdump (score: 1): Author: xxxx>; Date: Wed, 25 Apr 2001 14:22:47 -0600 (MDT); I have been trying to backup xfs partitions using amanda, and there seems to be a problem with xfsdump. Amanda suprisingly recognized xfsdump and seems to tried to do the backup correctly. On the oth; /archives/xfs/2001-04/msg01268.html (8,666 bytes)
14. Re: Errors using amanda/xfsdump (score: 1): Author: xxxx>; Date: Wed, 25 Apr 2001 15:39:19 -0500; Hmm, the xfs process is the x font server, nothing directly to do with xfs itself. However, obviously xfs is at the back of your problem. Can you provide a backtrace from kdb after it drops into the; /archives/xfs/2001-04/msg01269.html (10,358 bytes)
15. Re: Errors using amanda/xfsdump (score: 1): Author: xxxx>; Date: Wed, 25 Apr 2001 14:46:17 -0600 (MDT); I meant to say that the process 803 was xfsdump. Sorry. I had a brain cramp there ... .justin. -- Justin Leonard Tripp justin@xxxxxxxxxx Configurable Computing Laboratory Research Assistant CB 461 x8; /archives/xfs/2001-04/msg01270.html (11,253 bytes)
16. Re: Errors using amanda/xfsdump (score: 1): Author: xxxx>; Date: Thu, 26 Apr 2001 13:19:11 -0500; Having thought about this some more, I think the problem is being caused by the combination of local and remote access to the same files - lookups coming in from both directions in parallel almost in; /archives/xfs/2001-04/msg01287.html (10,296 bytes)
17. Errors using amanda/xfsdump (score: 1): Author: Justin Tripp <justin@xxxxxxxxx>; Date: Wed, 25 Apr 2001 14:22:47 -0600 (MDT); I have been trying to backup xfs partitions using amanda, and there seems to be a problem with xfsdump. Amanda suprisingly recognized xfsdump and seems to tried to do the backup correctly. On the oth; /archives/xfs/2001-04/msg01950.html (8,666 bytes)
18. Re: Errors using amanda/xfsdump (score: 1): Author: Steve Lord <lord@xxxxxxx>; Date: Wed, 25 Apr 2001 15:39:19 -0500; Hmm, the xfs process is the x font server, nothing directly to do with xfs itself. However, obviously xfs is at the back of your problem. Can you provide a backtrace from kdb after it drops into the; /archives/xfs/2001-04/msg01951.html (10,447 bytes)
19. Re: Errors using amanda/xfsdump (score: 1): Author: Justin Tripp <justin@xxxxxxxxx>; Date: Wed, 25 Apr 2001 14:46:17 -0600 (MDT); I meant to say that the process 803 was xfsdump. Sorry. I had a brain cramp there ... .justin. -- Justin Leonard Tripp justin@xxxxxxxxxx Configurable Computing Laboratory Research Assistant CB 461 x8; /archives/xfs/2001-04/msg01952.html (11,285 bytes)
20. Re: Errors using amanda/xfsdump (score: 1): Author: Steve Lord <lord@xxxxxxx>; Date: Thu, 26 Apr 2001 13:19:11 -0500; Having thought about this some more, I think the problem is being caused by the combination of local and remote access to the same files - lookups coming in from both directions in parallel almost in; /archives/xfs/2001-04/msg01969.html (10,385 bytes)

Current List: 1 - 20
Page: [1]