Hello Ed,
Thanks for the tip, it's highly appreciated as a solution! Goob job.
But I'd like Dell to move and fix that directly in their products.
Cordialement| Kind regards
Quentin Clarenne, Associate Director
4416 Louis B Mayer, Laval, Québec H7P 0G1
TEL : +1.514.360. 1802 (direct)
CA/US : 1.855.774.4678
FR : 01 76 60 41 43
UK : 0808 189 0423
AVIS: Ce courriel est confidentiel et peut être l'objet de secret
professionnel. Tout usage ou diffusion de celui-ci par une personne autre que
son destinataire est illégal. Si vous recevez ce courriel par erreur, veuillez
nous en aviser sans délai.
This message is confidential. It may also be privileged or otherwise protected
by work product immunity or other legal rules. If you have received it by
mistake, please let us know by e-mail reply and delete it from your system; you
may not copy this message or disclose its contents to anyone. Please send us by
fax any message containing deadlines as incoming e-mails are not screened for
response deadlines. The integrity and security of this message cannot be
guaranteed on the Internet.
Le 24/04/2017 à 11:44, Ed Velez a écrit :
I previously posted the following to the list as a temp
workaround...still no fix from what i can see. I'm curious if the
april updates will contain an update to the omsa tools addressing the
issue.
##############################################################
I have created a udev rule/hack to address this in the interim:
1) umount /tmp/SECUPD # as many times as you need to in order to fix
existing mounts
2) Create /etc/udev/rules.d/99-dell-tmp-secupd-fix.rules with the rule
corresponding to your distro:
rhel/cent 7:
# Fix to ensure /tmp/SECUPD is properly unmounted when the idrac usb
device is disconnected prior to being unmounted.
ACTION=="remove", ENV{ID_VENDOR}=="iDRAC", ENV{ID_TYPE}=="disk",
ENV{ID_FS_LABEL}="SECUPD", RUN+="/bin/sh -c '/bin/systemctl is-active
tmp-SECUPD.mount 1>/dev/null 2>&1; [[ $? -eq 0 ]] && /bin/logger
Unmounting /tmp/SECUPD: See
/etc/udev/rules.d/99-dell-tmp-secupd-fix.rules && /bin/systemctl stop
tmp-SECUPD.mount'"
rhel/cent 6:
# Fix to ensure /tmp/SECUPD is properly unmounted when the idrac usb
device is disconnected prior to being unmounted.
ACTION=="remove", ENV{ID_VENDOR}=="iDRAC", ENV{ID_TYPE}=="disk",
ENV{ID_FS_LABEL}="SECUPD", RUN+="/bin/sh -c '/bin/findmnt /tmp/SECUPD
1>/dev/null 2>&1; [[ $? -eq 0 ]] && /bin/logger Unmounting
/tmp/SECUPD: See /etc/udev/rules.d/99-dell-tmp-secupd-fix.rules &&
/bin/umount -fli /tmp/SECUPD'"
3) udevadm control --reload-rules
The rule is only trigged when the device is removed and is pretty
explicit so I feel it to be fairly safe. You can test by running
'srvadmin-services.sh restart' or just calling the invcol script
directly /opt/dell/srvadmin/sbin/invcol and verifying no mounts exist.
*From: *<[email protected]> on behalf of "Quentin C."
<[email protected]>
*Date: *Monday, April 24, 2017 at 10:15 AM
*To: *"[email protected]" <[email protected]>
*Subject: *Re: [Linux-PowerEdge] OSMA update to 8.4.0 issue
(Input/output error with /tmp/SECUPD)
Hi Dell,
Still no news of this bug reported several months ago? Do you still
have people working to update this system?
root@DELL [~]# df -h
df: `/tmp/SECUPD': Input/output error
df: `/tmp/SECUPD': Input/output error
root@DELL [~]# tail /var/log/messages
Apr 24 17:09:50 DELL kernel: [255105.555060] FAT: Directory
bread(block 5) failed
Apr 24 17:09:50 DELL kernel: [255105.555190] FAT: Directory
bread(block 6) failed
Apr 24 17:09:50 DELL kernel: [255105.555314] FAT: Directory
bread(block 7) failed
Apr 24 17:09:50 DELL kernel: [255105.555440] FAT: Directory
bread(block 8) failed
Apr 24 17:09:50 DELL kernel: [255105.555566] FAT: Directory
bread(block 9) failed
Apr 24 17:09:50 DELL kernel: [255105.555691] FAT: Directory
bread(block 10) failed
Apr 24 17:09:50 DELL kernel: [255105.555840] FAT: Directory
bread(block 11) failed
Apr 24 17:09:50 DELL kernel: [255105.555967] FAT: Directory
bread(block 12) failed
Apr 24 17:09:50 DELL kernel: [255105.556094] FAT: Directory
bread(block 13) failed
Apr 24 17:09:50 DELL kernel: [255105.556218] FAT: Directory
bread(block 14) failed
Apr 24 17:09:50 DELL kernel: [255105.556342] FAT: Directory
bread(block 15) failed
Apr 24 17:09:50 DELL kernel: [255105.556468] FAT: Directory
bread(block 16) failed
Apr 24 17:09:50 DELL kernel: [255105.556593] FAT: Directory
bread(block 17) failed
Apr 24 17:09:50 DELL kernel: [255105.556718] FAT: Directory
bread(block 18) failed
Apr 24 17:09:50 DELL kernel: [255105.556852] FAT: Directory
bread(block 19) failed
Apr 24 17:09:50 DELL kernel: [255105.556988] FAT: Directory
bread(block 20) failed
Apr 24 17:09:50 DELL kernel: [255105.557114] FAT: Directory
bread(block 21) failed
Apr 24 17:09:50 DELL kernel: [255105.557239] FAT: Directory
bread(block 22) failed
Apr 24 17:09:50 DELL kernel: [255105.557365] FAT: Directory
bread(block 23) failed
Apr 24 17:09:50 DELL kernel: [255105.557491] FAT: Directory
bread(block 24) failed
Apr 24 17:09:50 DELL kernel: [255105.557617] FAT: Directory
bread(block 25) failed
Apr 24 17:09:50 DELL kernel: [255105.557744] FAT: Directory
bread(block 26) failed
Apr 24 17:09:50 DELL kernel: [255105.557878] FAT: Directory
bread(block 27) failed
Apr 24 17:09:50 DELL kernel: [255105.558012] FAT: Directory
bread(block 28) failed
Apr 24 17:09:50 DELL kernel: [255105.558138] FAT: Directory
bread(block 29) failed
Apr 24 17:09:50 DELL kernel: [255105.558263] FAT: Directory
bread(block 30) failed
Apr 24 17:09:50 DELL kernel: [255105.558388] FAT: Directory
bread(block 31) failed
Apr 24 17:09:50 DELL kernel: [255105.558513] FAT: Directory
bread(block 32) failed
Apr 24 17:09:50 DELL kernel: [255105.558639] FAT: Directory
bread(block 33) failed
Apr 24 17:09:50 DELL kernel: [255105.558762] FAT: Directory
bread(block 34) failed
Apr 24 17:09:50 DELL kernel: [255105.558896] FAT: Directory
bread(block 35) failed
Apr 24 17:09:50 DELL kernel: [255105.559031] FAT: Directory
bread(block 36) failed
Could you at least give us a temporary solution/workarround or a
return about this issue ?
Cordialement| Kind regards
Quentin Clarenne, Associate Director
4416 Louis B Mayer, Laval, Québec H7P 0G1
TEL : +1.514.360. 1802 (direct)
CA/US : 1.855.774.4678
FR : 01 76 60 41 43
UK : 0808 189 0423
AVIS: Ce courriel est confidentiel et peut être l'objet de secret
professionnel. Tout usage ou diffusion de celui-ci par une personne autre que
son destinataire est illégal. Si vous recevez ce courriel par erreur, veuillez
nous en aviser sans délai.
This message is confidential. It may also be privileged or otherwise protected
by work product immunity or other legal rules. If you have received it by
mistake, please let us know by e-mail reply and delete it from your system; you
may not copy this message or disclose its contents to anyone. Please send us by
fax any message containing deadlines as incoming e-mails are not screened for
response deadlines. The integrity and security of this message cannot be
guaranteed on the Internet.
Le 17/11/2016 à 17:18, Quentin C. a écrit :
Hi !
Do you have a changelog for the dell-system-update 1.3.1-16.11.00 ?
Updated:
dell-system-update.x86_64 0:1.3.1-16.11.00
Complete!
root@DELL[~]# df -h
df: `/tmp/SECUPD': Input/output error
df: `/tmp/SECUPD': Input/output error
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 909G 232G 631G 27% /
tmpfs 24G 4.0K 24G 1% /dev/shm
Regards.
Cordialement| Kind regards
Quentin Clarenne, Associate Director
4416 Louis B Mayer, Laval, Québec H7P 0G1
TEL : +1.514.360. 1802 (direct)
CA/US : 1.855.774.4678
FR : 01 76 60 41 43
UK : 0808 189 0423
AVIS: Ce courriel est confidentiel et peut être l'objet de secret
professionnel. Tout usage ou diffusion de celui-ci par une personne autre que
son destinataire est illégal. Si vous recevez ce courriel par erreur, veuillez
nous en aviser sans délai.
This message is confidential. It may also be privileged or otherwise
protected by work product immunity or other legal rules. If you have received
it by mistake, please let us know by e-mail reply and delete it from your
system; you may not copy this message or disclose its contents to anyone.
Please send us by fax any message containing deadlines as incoming e-mails are
not screened for response deadlines. The integrity and security of this message
cannot be guaranteed on the Internet.
Le 11/11/2016 à 12:46, Quentin C. a écrit :
Hi Dell user/sys-admin !
Since the update of the Dell OMSA (srvadmin*) we have an issue
with the tmp mount point "/tmp/SECUPD"
If you have we have the latest OMSA version:
root@DELL [~]# rpm -qa | grep srvadmin
srvadmin-deng-8.4.0-2193.9883.el6.x86_64
...
srvadmin-idrac-snmp-8.4.0-2193.9883.el6.x86_64
root@DELL [~]# yum update
Loaded plugins: fastestmirror, rhnplugin
Setting up Update Process
Loading mirror speeds from cached hostfile
....
No Packages marked for Update
----------------
root@DELL [~]# df -h
df: `/tmp/SECUPD': Input/output error
df: `/tmp/SECUPD': Input/output error
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 227G 158G 58G 74% /
tmpfs 24G 84K 24G 1% /dev/shm
/dev/sdb1 1.8T 1.6T 151G 92% /home
/usr/tmpDSK 4.0G 838M 3.0G 22% /tmp
Flood in /var/log/message
Nov 11 18:29:04 DELL kernel: [507619.506195] FAT: FAT read
failed (blocknr 1)
Nov 11 18:31:26 DELL kernel: [507761.487934] FAT: FAT read
failed (blocknr 1)
Nov 11 18:31:26 DELL kernel: [507761.488134] FAT: FAT read
failed (blocknr 1)
Nov 11 18:33:26 DELL kernel: [507881.626283] FAT:
Directory bread(block 5) failed
Nov 11 18:33:26 DELL kernel: [507881.626410] FAT:
Directory bread(block 6) failed
Nov 11 18:33:26 DELL kernel: [507881.626532] FAT:
Directory bread(block 7) failed
Nov 11 18:33:26 DELL kernel: [507881.626653] FAT:
Directory bread(block 8) failed
Nov 11 18:33:26 DELL kernel: [507881.626785] FAT:
Directory bread(block 9) failed
Nov 11 18:33:26 DELL kernel: [507881.626908] FAT:
Directory bread(block 10) failed
Nov 11 18:33:26 DELL kernel: [507881.627028] FAT:
Directory bread(block 11) failed
Nov 11 18:33:26 DELL kernel: [507881.627149] FAT:
Directory bread(block 12) failed
Nov 11 18:33:26 DELL kernel: [507881.627271] FAT:
Directory bread(block 13) failed
Nov 11 18:33:26 DELL kernel: [507881.627391] FAT:
Directory bread(block 14) failed
Nov 11 18:33:26 DELL kernel: [507881.627512] FAT:
Directory bread(block 15) failed
Nov 11 18:33:26 DELL kernel: [507881.627634] FAT:
Directory bread(block 16) failed
Nov 11 18:33:26 DELL kernel: [507881.627755] FAT:
Directory bread(block 17) failed
Nov 11 18:33:26 DELL kernel: [507881.627883] FAT:
Directory bread(block 18) failed
Nov 11 18:33:26 DELL kernel: [507881.628007] FAT:
Directory bread(block 19) failed
Nov 11 18:33:26 DELL kernel: [507881.628130] FAT:
Directory bread(block 20) failed
Nov 11 18:33:26 DELL kernel: [507881.628255] FAT:
Directory bread(block 21) failed
Nov 11 18:33:26 DELL kernel: [507881.628378] FAT:
Directory bread(block 22) failed
Nov 11 18:33:26 DELL kernel: [507881.628500] FAT:
Directory bread(block 23) failed
Nov 11 18:33:26 DELL kernel: [507881.628621] FAT:
Directory bread(block 24) failed
Nov 11 18:33:26 DELL kernel: [507881.628745] FAT:
Directory bread(block 25) failed
Nov 11 18:33:26 DELL kernel: [507881.628870] FAT:
Directory bread(block 26) failed
Nov 11 18:33:26 DELL kernel: [507881.628996] FAT:
Directory bread(block 27) failed
Nov 11 18:33:26 DELL kernel: [507881.629119] FAT:
Directory bread(block 28) failed
Nov 11 18:33:26 DELL kernel: [507881.629243] FAT:
Directory bread(block 29) failed
Nov 11 18:33:26 DELL kernel: [507881.629365] FAT:
Directory bread(block 30) failed
Nov 11 18:33:26 DELL kernel: [507881.629489] FAT:
Directory bread(block 31) failed
Nov 11 18:33:26 DELL kernel: [507881.629611] FAT:
Directory bread(block 32) failed
Nov 11 18:33:26 DELL kernel: [507881.629735] FAT:
Directory bread(block 33) failed
Nov 11 18:33:26 DELL kernel: [507881.629862] FAT:
Directory bread(block 34) failed
Nov 11 18:33:26 DELL kernel: [507881.629987] FAT:
Directory bread(block 35) failed
Nov 11 18:33:26 DELL kernel: [507881.630109] FAT:
Directory bread(block 36) failed
Nov 11 18:34:07 DELL kernel: [507922.227656] FAT: FAT read
failed (blocknr 1)
I tried in the past to stop the srvadmin service, unmount the
/tmp/SECUPD like this:
srvadmin-services.sh stop
lsof +D /tmp/SECUPD/
umount /tmp/SECUPD
umount /tmp/SECUPD
rmdir /tmp/SECUPD
srvadmin-services.sh start
But when we restart the DELL server, the issue is coming again.
I view in old poweredge message something like "We have fixed
this issue and fix will be available in the next OMSA
release." but do you have some news/ETA ?
Regards.
Quentin
--
Cordialement| Kind regards
Quentin Clarenne, Associate Director
4416 Louis B Mayer, Laval, Québec H7P 0G1
TEL : +1.514.360. 1802 (direct)
CA/US : 1.855.774.4678
FR : 01 76 60 41 43
UK : 0808 189 0423
AVIS: Ce courriel est confidentiel et peut être l'objet de secret
professionnel. Tout usage ou diffusion de celui-ci par une personne autre que
son destinataire est illégal. Si vous recevez ce courriel par erreur, veuillez
nous en aviser sans délai.
This message is confidential. It may also be privileged or otherwise
protected by work product immunity or other legal rules. If you have received
it by mistake, please let us know by e-mail reply and delete it from your
system; you may not copy this message or disclose its contents to anyone.
Please send us by fax any message containing deadlines as incoming e-mails are
not screened for response deadlines. The integrity and security of this message
cannot be guaranteed on the Internet.
_______________________________________________
Linux-PowerEdge mailing list
[email protected] <mailto:[email protected]>
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
_______________________________________________
Linux-PowerEdge mailing list
[email protected] <mailto:[email protected]>
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
_______________________________________________
Linux-PowerEdge mailing list
[email protected]
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
