Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Reserve space for metadata #1

Closed
gila opened this issue Sep 16, 2019 · 1 comment
Closed

Reserve space for metadata #1

gila opened this issue Sep 16, 2019 · 1 comment
Assignees
@gila

Comments

@gila
Copy link
Contributor

gila commented Sep 16, 2019

The nexus driver should, implicitly, reserve disk space for metadata. The metadata is used during the rebuild process.
@gila gila self-assigned this Sep 16, 2019
@gila gila changed the title ## Reserve space for metadata Reserve space for metadata Sep 16, 2019
@gila gila mentioned this issue Oct 7, 2019
Merged
@gila
Copy link
Contributor Author

gila commented Oct 7, 2019

Implemented by #7

@gila gila closed this as completed Oct 7, 2019
tjoshum pushed a commit that referenced this issue Mar 10, 2020
@blaisedias
Merge pull request #1 from tjoshum/cas21
04227bd 
CAS-21 Add ShareProtocol field to PublishNexusRequest
tiagolobocastro added a commit that referenced this issue Mar 17, 2020
@tiagolobocastro
Simple rebuild cas 37 36 (#1)
e6d6320 
Adding a simple/noddy rebuild and its test

Rebuild up to 10MiB of the child to avoid timing out the js tests: this is temporary until we move the rebuild trigger to another thread context

Add a test case for the rebuild within the add_child rpc call:
1 - create/start a nexus with 1 child
2 - dd from urandom into the nexus
3 - verify (cmp) that the child has the right data
5 - verify (cmp) that a new child (to be added) has the wrong data
4 - add the new child and wait for rebuild
5 - verify (cmp) that the new child has the right data

CAS-37: On child added fully rebuild from another healthy child on the same context with no frontend IO
CAS-36: Develop the first test case for the child added rebuild process
tiagolobocastro added a commit that referenced this issue Mar 18, 2020
@tiagolobocastro
Simple rebuild cas 37 36 (#1)
6fe3257 
Adding a simple/noddy rebuild and its test

Rebuild up to 10MiB of the child to avoid timing out the js tests: this is temporary until we move the rebuild trigger to another thread context

Add a test case for the rebuild within the add_child rpc call:
1 - create/start a nexus with 1 child
2 - dd from urandom into the nexus
3 - verify (cmp) that the child has the right data
5 - verify (cmp) that a new child (to be added) has the wrong data
4 - add the new child and wait for rebuild
5 - verify (cmp) that the new child has the right data

CAS-37: On child added fully rebuild from another healthy child on the same context with no frontend IO
CAS-36: Develop the first test case for the child added rebuild process
yannis218 added a commit that referenced this issue Mar 20, 2020
@yannis218
Merge pull request #1 from openebs/master
f766122 
Pull from main.
gila added a commit that referenced this issue Sep 16, 2020
@gila
session #1 go over the internal states
5706a3c
paulyoong referenced this issue in paulyoong/Mayastor Sep 23, 2020
@gila
session #1 go over the internal states
b8d9298
paulyoong referenced this issue in paulyoong/Mayastor Sep 28, 2020
@gila
session #1 go over the internal states
00bfd12
blaisedias added a commit that referenced this issue Dec 10, 2020
@blaisedias
Address review comments #1.
454350e
@Hoverbear Hoverbear mentioned this issue Feb 17, 2021
Merged
jkryl pushed a commit that referenced this issue May 26, 2021
fix(moac): timeouts when updating volume custom resource
118f61a 
The problem was that the objects (old and new one) were basically
the same except that order of entries in replicas array was different.
Problem #1 is that we do useless update of CR and #2 is that k8s
does not emit mod event in such case so volume-operator was timing
out waiting for the event.

The fix is to enforce deterministic order of entries in replicas
array so that deep-equal compares the objects correctly.
@jkryl jkryl mentioned this issue May 26, 2021
Merged
bors bot pushed a commit that referenced this issue May 26, 2021
Merge #901
011003f 
901: fix(moac): timeouts when updating volume custom resource r=jkryl a=jkryl

The problem was that the objects (old and new one) were basically
the same except that order of entries in replicas array was different.
Problem #1 is that we do useless update of CR and #2 is that k8s
does not emit mod event in such case so volume-operator was timing
out waiting for the event.

The fix is to enforce deterministic order of entries in replicas
array so that deep-equal compares the objects correctly.

Co-authored-by: Jan Kryl <jan.kryl@mayadata.io>
dsavitskiy added a commit to dsavitskiy/mayastor that referenced this issue Oct 5, 2021
@dsavitskiy
wip - device event listener refactoring openebs#1
7811614
dsavitskiy added a commit to dsavitskiy/mayastor that referenced this issue Oct 5, 2021
@dsavitskiy
wip - device event listener refactoring openebs#1
ba68fc8
dsavitskiy added a commit to dsavitskiy/mayastor that referenced this issue Oct 7, 2021
@dsavitskiy
wip - device event listener refactoring openebs#1
8f231a8
dsavitskiy added a commit to dsavitskiy/mayastor that referenced this issue Oct 11, 2021
@dsavitskiy
wip - device event listener refactoring openebs#1
d58b18b
dsavitskiy added a commit to dsavitskiy/mayastor that referenced this issue Oct 12, 2021
@dsavitskiy
wip - device event listener refactoring openebs#1
0fe6087
dsavitskiy added a commit to dsavitskiy/mayastor that referenced this issue Oct 25, 2021
@dsavitskiy
wip - device event listener refactoring openebs#1
d1d6b6e
dsavitskiy added a commit to dsavitskiy/mayastor that referenced this issue Oct 25, 2021
@dsavitskiy
wip - device event listener refactoring openebs#1
e37b973
dsavitskiy added a commit to dsavitskiy/mayastor that referenced this issue Nov 2, 2021
@dsavitskiy
wip - fixing device event routing openebs#1
44eedb6
dsavitskiy added a commit to dsavitskiy/mayastor that referenced this issue Nov 8, 2021
@dsavitskiy
wip - lifetime for Nexus openebs#1: all static
eac1f23
@luginbash luginbash mentioned this issue May 11, 2022
Closed
paulyoong pushed a commit that referenced this issue May 27, 2022
@blaisedias
Merge #1
ccaf3a5 
1: refactor: update commit linter

Co-authored-by: Blaise Dias <blaise.dias@mayadata.io>
@evilezh evilezh mentioned this issue Aug 11, 2022
Closed
dsavitskiy added a commit that referenced this issue Nov 10, 2022
@dsavitskiy
feat(debug): new diag added #1
ddf9e57 
Signed-off-by: Dmitry Savitskiy <dmitry.savitskiy@datacore.com>
dsavitskiy added a commit that referenced this issue Nov 17, 2022
@dsavitskiy
feat(debug): adminq poller diag #1
d727f93 
Signed-off-by: Dmitry Savitskiy <dmitry.savitskiy@datacore.com>
dsavitskiy added a commit that referenced this issue Nov 17, 2022
@dsavitskiy
feat(debug): new diag added #1
e2e1572 
Signed-off-by: Dmitry Savitskiy <dmitry.savitskiy@datacore.com>
dsavitskiy added a commit that referenced this issue Nov 17, 2022
@dsavitskiy
feat(debug): adminq poller diag #1
c9a3064 
Signed-off-by: Dmitry Savitskiy <dmitry.savitskiy@datacore.com>
@cjyar cjyar mentioned this issue Apr 10, 2023
Closed
@dsavitskiy dsavitskiy mentioned this issue Aug 18, 2023
Merged
@joselbr2099 joselbr2099 mentioned this issue Oct 18, 2023
Closed
dsavitskiy added a commit to dsavitskiy/mayastor that referenced this issue Oct 28, 2023
@dsavitskiy
feat(nvmf): selecting different CRD for replicas and certain nexus er…
f9e5a81 
…rors

NVMF subsystem will select different preconfigured CRDs for certain cases:
openebs#1 is selected for all errors on nexus target except ENOSPC and
  reservation conflict
openebs#2 is selected for ENOSPC and reservation conflict errors on nexus targets
openebs#3 is selected for replica targets

Signed-off-by: Dmitry Savitskiy <dmitry.savitskiy@datacore.com>
@ThorbenJ ThorbenJ mentioned this issue Jul 10, 2024
Closed
@innotecsol innotecsol mentioned this issue Oct 27, 2024
Closed
@Liana64 Liana64 mentioned this issue Oct 29, 2024
Open
@ming135 ming135 mentioned this issue Dec 27, 2024
Open
@daudcanugerah daudcanugerah mentioned this issue Jan 24, 2025
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gila gila

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gila