Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Recovering\s+Linux\s+TSM\s+server\s+from\s+partial\s+filesystem\s+failure\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Recovering\s+Linux\s+TSM\s+server\s+from\s+partial\s+filesystem\s+failure\s*$/: 12 ]

Total 12 documents matching your query.

1. [ADSM-L] Recovering Linux TSM server from partial filesystem failure (score: 1): Author: Zoltan Forray <zforray AT VCU DOT EDU>; Date: Mon, 10 Mar 2014 10:55:47 -0400; We recently had our offsite/recover TSM server (RH Linux 6.4, TSM 6.3.4.200) go south. Something happened that caused DB2 to start crashing/dumping and subsequently completely filled the filesystem c; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2014-03/msg00029.html (13,433 bytes)
2. Re: [ADSM-L] Recovering Linux TSM server from partial filesystem failure (score: 1): Author: "Arbogast, Warren K" <warbogas AT IU DOT EDU>; Date: Mon, 10 Mar 2014 15:09:24 +0000; Zoltan, We are all eager to know if the something that happened had anything to do with TSM 6.3.2 or DB2. Since they seem to be fine and the OS needs to be rebuilt, presumably not. Sometimes i's and; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2014-03/msg00030.html (14,434 bytes)
3. Re: [ADSM-L] Recovering Linux TSM server from partial filesystem failure (score: 1): Author: Zoltan Forray <zforray AT VCU DOT EDU>; Date: Mon, 10 Mar 2014 11:57:43 -0400; As soon as I know more, I will post here. My OS guy (offsite with the box) just reported/confirmed the root filesystem is a loss and will have to rebuild/reinstall. He is running Dell hardware diagno; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2014-03/msg00031.html (19,457 bytes)
4. Re: [ADSM-L] Recovering Linux TSM server from partial filesystem failure (score: 1): Author: Zoltan Forray <zforray AT VCU DOT EDU>; Date: Tue, 11 Mar 2014 11:17:51 -0400; With the lack of replies, I am guessing I can't recover this server from what is left behind. I do have an old DB backups but for what this server does, it isn't worth bothering. I can rebuild it fas; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2014-03/msg00047.html (22,454 bytes)
5. Re: [ADSM-L] Recovering Linux TSM server from partial filesystem failure (score: 1): Author: Chavdar Cholev <chavdar.cholev AT GMAIL DOT COM>; Date: Tue, 11 Mar 2014 18:18:45 +0200; Zoltan, you can check db2diag log fir more info, I would start from there. I am nor sure about TSM6.1 to TSM7.1, my main concern here is different DB2 versions. If you thing to rebuild TSM 6.1 on new; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2014-03/msg00049.html (22,192 bytes)
6. Re: [ADSM-L] Recovering Linux TSM server from partial filesystem failure (score: 1): Author: Chavdar Cholev <chavdar.cholev AT GMAIL DOT COM>; Date: Tue, 11 Mar 2014 18:21:57 +0200; Zoltan, if not you can check here: http://www-01.ibm.com/support/docview.wss?uid=swg21420318 On 3/11/2014 17:17, Zoltan Forray wrote: With the lack of replies, I am guessing I can't recover this serv; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2014-03/msg00050.html (22,089 bytes)
7. Re: [ADSM-L] Recovering Linux TSM server from partial filesystem failure (score: 1): Author: Zoltan Forray <zforray AT VCU DOT EDU>; Date: Tue, 11 Mar 2014 12:52:46 -0400; The db2diag.log file was lost along with the root and /home partition. All I have is ghost messages from the activity log (TSMManager console saves a lot of the messages in its buffers) -- *Zoltan Fo; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2014-03/msg00051.html (25,993 bytes)
8. Re: [ADSM-L] Recovering Linux TSM server from partial filesystem failure (score: 1): Author: Thomas Denier <Thomas.Denier AT JEFFERSONHOSPITAL DOT ORG>; Date: Tue, 11 Mar 2014 13:43:50 -0400; --Zoltan Forray wrote: -- Google would normally treat a minus sign as a request for Web pages not containing a specific word, so that a search for 'sqlcode -980' would find pages containing 'sqlcode'; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2014-03/msg00052.html (13,695 bytes)
9. Re: [ADSM-L] Recovering Linux TSM server from partial filesystem failure (score: 1): Author: Skylar Thompson <skylar2 AT U.WASHINGTON DOT EDU>; Date: Tue, 11 Mar 2014 10:49:11 -0700; Encapsulating the term in quotes ("-980") ought to do the trick. Looks like -980 is associated with a disk error, which unfortunately doesn't help Zoltan too much at this point... http://publib.bould; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2014-03/msg00053.html (13,779 bytes)
10. Re: [ADSM-L] Recovering Linux TSM server from partial filesystem failure (score: 1): Author: Zoltan Forray <zforray AT VCU DOT EDU>; Date: Tue, 11 Mar 2014 15:07:24 -0400; Thanks for finding that but, as you said, it doesn't help much. The disk filled to 100% due to DB2 taking dumps but that doesn't tell me what caused the dumping in the first place. We are still runni; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2014-03/msg00056.html (15,202 bytes)
11. Re: [ADSM-L] Recovering Linux TSM server from partial filesystem failure (score: 1): Author: Skylar Thompson <skylar2 AT U.WASHINGTON DOT EDU>; Date: Tue, 11 Mar 2014 13:15:22 -0700; Since you mentioned Dell, one thing to check would be PERC and hard drive firmware levels. There have been a number of updates to both over the past few years concerning silent data corruption under; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2014-03/msg00057.html (13,922 bytes)
12. Re: [ADSM-L] Recovering Linux TSM server from partial filesystem failure (score: 1): Author: Zoltan Forray <zforray AT VCU DOT EDU>; Date: Wed, 12 Mar 2014 09:07:21 -0400; Thanks for the suggestion. As SOP, we update all firmware, every few months, so this box is up-to-date. The Dell diagnostics finally finished, CLEAN. No issues found. I have some of the FODC logs whe; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2014-03/msg00060.html (15,131 bytes)

Current List: 1 - 12
Page: [1]