Zoltan,
Would it be acceptable to just force an unmount of the ghost FS ?
I had a similar situation where a vendor was hired to perform some analytics on
our 150 Linux servers, his removal process failed, leaving the mount points.
For me that was easier......
-Rick Adamson
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Zoltan Forray
Sent: Tuesday, February 07, 2017 4:07 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] How to exclude bad Linux mountpoint
Thanks for the suggestions. I forgot about the EXCLUDE.FS which seems to have
done the trick since it is a filesystem (see df below). Now to roll this out
to all of my Linux servers.
[zforray@processor ~]$ df -m
Filesystem 1M-blocks Used Available Use% Mounted on
/dev/mapper/vg_processr_sys-lv_root
20031 7123 11885 38% /
tmpfs 48339 1 48339 1% /dev/shm
/dev/sdb2 477 108 344 24% /boot
/dev/sdb1 100 1 100 1% /boot/efi
/dev/mapper/vg_processr_sys-lv_home
50269 10818 36891 23% /home
/dev/mapper/vg_processr_sys-lv_tsmarchlog
302380 480 301901 1% /tsmdb2
/dev/mapper/vg_processr_sys-lv_tsmarchlog2
151190 348 150843 1% /tsmarchlog2
/dev/mapper/vg_processr_sys-lv_tsmdb
403174 364843 38331 91% /tsmdb
/dev/mapper/vg_processr_sys-lv_tsmlog
129016 120165 2298 99% /tsmlog
/dev/mapper/vg_processr_pool-lv_tsmpool
10133861 9618741 344 100% /tsmpool
/dev/mapper/vg_processr_sys-lv_var
14991 878 13346 7% /var
/dev/sdd 2 0 2 0% /tmp/SECUPD
/dev/sde 2 0 2 0% /tmp/SECUPD
On Tue, Feb 7, 2017 at 3:05 PM, Andrew Raibeck <storman AT us.ibm DOT com>
wrote:
> Hi Zoltan,
>
> It could be the simple act of enumerating file systems or mount points
> that causes a problem. What kinds of problems, specifically, are you seeing?
>
> A couple of thoughts (not sure these will help):
>
> - Does this show up as a separate file system, such as when you do df -m?
> If yes, you could try exclude.fs /tmp/SECUPD
>
> - Another possibility is to define it as a virtual mount point using
> the VIRTUALMOUNTPOINT option, then using exclude.fs.
>
> Finally, a total "shot in the dark", but try searching the internet
> for this directory name. One discussion I found indicates that
> /tmp/SECUPD is causing other issues, too:
>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__en.community.dell.com_support-2Dforums_servers_f_956_t_19996605&d=DwIGaQ&c=AzgFQeXLLKhxSQaoFCm29A&r=uJG3UnPaeoz9naeIzbwWFddVED8ETOYHxjoACoofi2Y&m=dpyZFjUm5jdJEy7vIroIPKAZVkonlHvpInjN-PV6Njo&s=emQBeN08TImOrf5CKuScl7Pu2yElvurRtxPTdEAeZps&e=
>
>
> Regards,
>
> Andy
>
> ____________________________________________________________
> ________________
>
> Andrew Raibeck | IBM Spectrum Protect Level 3 | storman AT us.ibm DOT com
>
> IBM Tivoli Storage Manager links:
> Product support:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ibm.com_support_entry_portal_product_tivoli_&d=DwIGaQ&c=AzgFQeXLLKhxSQaoFCm29A&r=uJG3UnPaeoz9naeIzbwWFddVED8ETOYHxjoACoofi2Y&m=dpyZFjUm5jdJEy7vIroIPKAZVkonlHvpInjN-PV6Njo&s=ECVSfVXW6qbUJh9K4NzdycKHtgKidb30DOkhhN3vnSg&e=
>
> tivoli_storage_manager
>
> Online documentation:
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ibm.com_support_knowledgecenter_SSGSG7_&d=DwIGaQ&c=AzgFQeXLLKhxSQaoFCm29A&r=uJG3UnPaeoz9naeIzbwWFddVED8ETOYHxjoACoofi2Y&m=dpyZFjUm5jdJEy7vIroIPKAZVkonlHvpInjN-PV6Njo&s=YvaXmgbA-vSR09gHC1JzvaVMgvi9HcpCk8dhEP9YuxA&e=
>
> landing/welcome_ssgsg7.html
>
> Product Wiki:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ibm.com_developerworks_community_wikis_home_wiki_Tivoli-25&d=DwIGaQ&c=AzgFQeXLLKhxSQaoFCm29A&r=uJG3UnPaeoz9naeIzbwWFddVED8ETOYHxjoACoofi2Y&m=dpyZFjUm5jdJEy7vIroIPKAZVkonlHvpInjN-PV6Njo&s=i2qIxt6CveEAE0hGbd2V-kpyTFpNQgBj7tu6ei3GDZY&e=
>
> 20Storage%20Manager
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2017-02-07
> 14:45:50:
>
> > From: Zoltan Forray <zforray AT VCU DOT EDU>
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Date: 2017-02-07 14:46
> > Subject: How to exclude bad Linux mountpoint Sent by: "ADSM: Dist
> > Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> >
> > Ever since a certain Dell update, a ghost mountpoint of /tmp/SECUPD
> > is
> left
> > hanging after iDRAC/OpenManage updates. This is now causing
> > heartburn
> for
> > TSM backups.
> >
> > I have tried pushing down via CLOPTSET to
> >
> > exclude.dir /tmp/SECUPD
> > exclude /tmp/SECUPD
> >
> > but neither work - TSM still tries to access/back it up.
> >
> > Any suggestions on how to get TSM to stop trying to access this mount?
> >
> >
> >
> >
> >
> > --
> > *Zoltan Forray*
> > Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator
> > Xymon Monitor Administrator VMware Administrator (in training)
> > Virginia Commonwealth University UCC/Office of Technology Services
> > www.ucc.vcu.edu zforray AT vcu DOT edu - 804-828-4807 Don't be a phishing
> > victim - VCU and other reputable organizations will never use email
> > to request that you reply with your password, social security number
> > or confidential personal information. For more details visit
> > https://urldefense.proofpoint.com/v2/url?u=http-3A__infosecurity.vcu.edu_phishing.html&d=DwIGaQ&c=AzgFQeXLLKhxSQaoFCm29A&r=uJG3UnPaeoz9naeIzbwWFddVED8ETOYHxjoACoofi2Y&m=dpyZFjUm5jdJEy7vIroIPKAZVkonlHvpInjN-PV6Njo&s=Jgph2Ob8sBrNBPhILS0CFBEOhU7YAAUwhGMLxxbhn_g&e=
> >
> >
>
--
*Zoltan Forray*
Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator Xymon Monitor
Administrator VMware Administrator (in training) Virginia Commonwealth
University UCC/Office of Technology Services www.ucc.vcu.edu zforray AT vcu DOT
edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable
organizations will never use email to request that you reply with your
password, social security number or confidential personal information. For more
details visit
https://urldefense.proofpoint.com/v2/url?u=http-3A__infosecurity.vcu.edu_phishing.html&d=DwIGaQ&c=AzgFQeXLLKhxSQaoFCm29A&r=uJG3UnPaeoz9naeIzbwWFddVED8ETOYHxjoACoofi2Y&m=dpyZFjUm5jdJEy7vIroIPKAZVkonlHvpInjN-PV6Njo&s=Jgph2Ob8sBrNBPhILS0CFBEOhU7YAAUwhGMLxxbhn_g&e=
|
