Error 2 Deleting Row From Table As.volume.status
CRASH WITH INTERNAL ERROR TMTXN008 DETECTED. AIX Subscribe You can track all active APARs for this component. APAR status Closed as unreproducible. Error description A condition has been observed within a LANFREE archive operation where the dsmc process appears to hang. When that process is canceled or the dsmc process is killed on the client system, the ITSM server will crash with the following stack. . ANR9999D pkthread.c(598): ThreadId<36> Run-time assertion failed: "txnP->txnInFlight", Thread 36, File tmtxn.c, Line 946. ANR7824S Server operation terminated. ANR7823S Internal error TMTXN008 detected. ANR9999D Trace-back of called functions: ANR9999D 0x0000000100068E1C pkAbort ANR9999D 0x0000000100068EA8 pkLogicAbort ANR9999D 0x0000000100A091CC tmAbort ANR9999D 0x000000010082E26C AbortStaTxn ANR9999D 0x000000010081EF7C SmDatabaseServerSession ANR9999D 0x0000000100785C38 DoDbServer ANR9999D 0x000000010077E9E4 smExecuteSession ANR9999D 0x000000010007D2C0 SessionThread ANR9999D 0x000000010006C974 StartThread ANR9999D 0xFFFFFFFF7EB1F35C *UNKNOWN* ANR9999D 0x000000010006C854 StartThread . The problem results when two threads attempt to end the same transaction. The problem has an internal defect number of 11815 and was corrected in all 5.2 servers. In addition the problem has not been observed in 5.1.8.0 level servers. - - - The changes made to fix the internal defect may also prevent the following error messages in some cases: ANR0106E asutil.c(646): Unexpected error 2 fetching row in table "AS.Volume.Status". ANR0104E (Session: number, Origin: storage_agent_name) astxn.c(xxxx): Error 17 deleting row from table "AS.Volume.Status" - - - Please review APAR IC38994 for information about correcting possible problems related to these messages. Local fix Use lan archive, or upgrade ITSM server to 5.1.8.0 or 5.2 Problem summary **************************************************************** * USERS AFFECTED: Any TSM server that is performing LAN-free * * data movement. * **************************************************************** * PROBLEM DESCRIPTION: The TSM server and storage agent may * * not correctly coordinate the * * termination and clean-up of an * * in-flight transaction in some cases. * * This incorrect handling of * * terminating an in-flight transaction * * may result in the server crashing. * * This may also result in damage to * * the database. One typical symptom * * of this damage is the following * * error message: * * * * ANR0106E asutil.c(646): Unexpected * * error 2 fetching row in table * * "AS.Volume.Status". * **********************************************************
Subscribe You can track all active APARs for this component. APAR status Closed as program error. Error description IC38940 documents a defect that may cause TSM Server crash or the following messages: ANR0106E asutil.c(xxx): Unexpected error 2 fetching row in table "AS.Volume.Status". ANR0104E (Session: number, Origin: storage_agent_name) astxn.c(xxxx): Error 17 deleting row from table "AS.Volume.Status" After this problem occurs, entries may be missing from the AS.Volume.Status table or the AS.Volume.Assignment table. A utility should be provided http://www.ibm.com/support/docview.wss?uid=swg1IC38940 to resolve these missing entries. Local fix Problem summary **************************************************************** * USERS AFFECTED: TSM server and storage agent users * * performing LAN-free data transfer * * operations prior to V5.1.8.0. * **************************************************************** * PROBLEM DESCRIPTION: A timing issue existed prior to * * V5.1.8.0. This timing window could * * result in multiple participants * * http://www.ibm.com/support/docview.wss?uid=swg1IC38994 trying to operate on the same * * transaction at the same time. * * Typically this was the result of * * the storage agent attempting to * * finish a transaction at the same * * time that the server decided to * * cancel the storage agent session * * because of the RESOURCETIMEOUT * * option setting. If this timing * * window was encountered, this could * * result in database entries being * * incorrect or missing as documented * * in the error description for * * this apar. * **************************************************************** * RECOMMENDATION: Apply fixing PTF when available. This * * problem is currently projected to be fixed * * in level 5.2.3 and 5.1.9. Note that this is * * subject to change at the discretion of IBM. * **************************************************************** The REPAIR STGVOL utility has been enhanced to identify and correct errors relating to the timing error that existed for LAN-Free operations being performed on servers and storage agents prior to V
●20 If i do cinder delete $volume_id i got an "error_deleting" and i cannot remove the volume! What can i do to force the remove of https://ask.openstack.org/en/question/1378/cannot-remove-volume/ it? edit retag flag offensive close merge delete add a comment 9 answers https://bugzilla.redhat.com/show_bug.cgi?id=888987 Sort by » oldest newest most voted 8 answered 2013-05-20 06:06:12 -0500 gfidente 239 ●4 ●5 ●9 http://giuliofidente.com/ You should really try to figure out why it is failing in the first place. Set debug=True and verbose=True in cinder.conf, restart the services and make a further delete attempt to see if error 2 anything useful pops up in the volume log file. You can also try using the cinder force-delete command, which bypasses some checks. Last but not least, if you're sure the volume isn't there anymore and there are no references to it (eg. in /etc/cinder/volumes), you can hack into the database and delete it from the volumes_metadata and volumes tables. edit flag offensive delete error 2 deleting link more CommentsThx for your answer! When i do cinder force-delete or cinder delete i got this message: [19332.031250] iscsi_trgt: iscsi_volume_del(303) 1 0. polslinux( 2013-05-20 11:53:41 -0500 )editi tried also to delete info from cinder db: delete from volumes where id="aaaaaaaaaaaa"; ERROR 1451 (23000): cannot delete or update a parent row: a foreign key constraint fails ('cinder'.'iscsi_targets', CONSTRAINT 'iscsi_targets_ibfk_1' FOREIGN KEY('volume_id') REFERENCES 'volumes' ('id'))polslinux( 2013-05-20 11:53:52 -0500 )edit@polslinux I'm not sure how you got into such a situation but still, ensures the volume target definition files have been deleted and are not imported into your tgtd config and then delete the volumes from the database ... also remove the volume from the foreign tablesgfidente( 2013-06-12 09:52:58 -0500 )editYou also may (but shouldn't) enforce deleting fom db: SET foreign_key_checks = 0; DELETE FROM ... SET foreign_key_checks = 1;laboshinl( 2013-10-25 06:49:37 -0500 )editThanks a lot for the guide. Cinder delete or force-delete didn't work for me. But I managed to resolve the problem by modifying the corresponding volume's status = "available", attachment_status="detached" in cinder.volumes and cinder.volume_attachment. Then cinder delete worked :)聪明健康( 2016-02-14 21:44:12 -0500 )editadd a comment 2 answered 2013-11-12 13:
-Clone This Bug -Last Comment First Last Prev Next This bug is not in your last search results. Bug888987 - Volume stuck in error_deleting Summary: Volume stuck in error_deleting Status: CLOSED ERRATA Aliases: None Product: Red Hat OpenStack Classification: Red Hat Component: python-cinderclient (Show other bugs) Sub Component: --- Version: 2.1 Hardware: Unspecified Unspecified Priority medium Severity medium TargetMilestone: snapshot4 TargetRelease: 2.1 Assigned To: Eric Harney QA Contact: Attila Fazekas Docs Contact: URL: Whiteboard: Keywords: Triaged Depends On: 896153 Blocks: Show dependency tree /graph Reported: 2012-12-19 18:35 EST by Graeme Gillies Modified: 2016-04-26 19:13 EDT (History) CC List: 2 users (show) eharney fpercoco See Also: Fixed In Version: 1.0.0.20-3 Doc Type: Bug Fix Doc Text: Story Points: --- Clone Of: Environment: Last Closed: 2013-03-21 15:03:58 EDT Type: Bug Regression: --- Mount Type: --- Documentation: --- CRM: Verified Versions: Category: --- oVirt Team: --- RHEL 7.3 requirements from Atomic Host: Cloudforms Team: --- Attachments (Terms of Use) Add an attachment (proposed patch, testcase, etc.) External Trackers Tracker ID Priority Status Summary Last Updated OpenStack gerrit 20064 None None None Never Groups: None (edit) Description Graeme Gillies 2012-12-19 18:35:18 EST Hi, Unfortunately somewhere along the line we had a failure to delete one of the volumes due to a permissions error. This threw some errors into the openstack log, and now when I do a cinder list --all-tenants I see +--------------------------------------+----------------+-------------------------+------+-------------+--------------------------------------+ | ID | Status | Display Name | Size | Volume Type | Attached to | +--------------------------------------+----------------+-------------------------+------+-------------+--------------------------------------+ | 3dc53676-81e7-4b5e-9b3c-f4603d2b2846 | error_deleting | testcinder | 1 | None | | +--------------------------------------+----------------+-------------------------+------+-------------+--------------------------------------+ The volume is setting there in error_deleting. I try to use cinder delete to get rid of it after fixing the problem, but it gives me a 400 error saying the volume is in a bad state. What is the best path to recover from this? Regards, Graeme Comment 2 Eric Harney 2012-12-20 12:30:30 EST Cinder only allows deletion when the volume is in certain states -- not including error_deleting. When this happens, you can remove the volume by logging int