Bug 53413 – Stop LDAP Transactions if disk space is full

Bug 53413 - Stop LDAP Transactions if disk space is full


Summary:	Stop LDAP Transactions if disk space is full

Status:	RESOLVED DUPLICATE of bug 50660

Product:	UCS
Classification:	Unclassified
Component:	LDAP
Version:	UCS 4.4
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2021-06-07 16:19 CEST by Dirk Schnick
Modified:	2021-06-07 16:56 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Feature Request
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2021060421000439
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Dirk Schnick

2021-06-07 16:19:56 CEST

A customer mentioned in the given ticket:

"Actually, it would also be nice if UCS did not get into this inconsistent state in the first place.
this inconsistent state in the first place.

How well something runs in the event of an error is also a part of the
quality of products.

I have had to deal with other software before (I think it was
'chef' or the couchdb under it), which only continued to work when there was
enough free disk space was available.
Read accesses could still work, but write accesses should simply be
should then simply be rejected."

I agree with this.
Problem was a broken transactionlog after var partition ran out of space. A not unusual scenario.

Comment 1 Philipp Hahn

2021-06-07 16:56:18 CEST


*** This bug has been marked as a duplicate of bug 50660 ***