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.

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

Mount error shouldn't be ignored #15

Open
cwen0 opened this issue Jan 15, 2021 · 2 comments
Open

Mount error shouldn't be ignored #15

cwen0 opened this issue Jan 15, 2021 · 2 comments
Labels
bug Something isn't working

Comments

@cwen0
Copy link
Member

cwen0 commented Jan 15, 2021

This error shouldn't be ignored:

[2021-01-14 20:24:11.338447 +08:00] INFO [toda::ptrace] src/ptrace/mod.rs:100: detach process: 5282 successfully
Error: source: /var/lib/mysql/data/mydata/wenlin/, target: /var/lib/mysql/data/mydata/__chaosfs__wenlin__

Caused by:
    EINVAL: Invalid argument

Stack backtrace:
   0: <E as anyhow::context::ext::StdError>::ext_context
             at ./root/.cargo/registry/src/github.com-1ecc6299db9ec823/anyhow-1.0.31/src/backtrace.rs:26
      anyhow::context::<impl anyhow::Context<T,E> for core::result::Result<T,E>>::context::{{closure}}
             at ./root/.cargo/registry/src/github.com-1ecc6299db9ec823/anyhow-1.0.31/src/context.rs:50
      core::result::Result<T,E>::map_err
             at ./rustc/16957bd4d3a5377263f76ed74c572aad8e4b7e59/src/libcore/result.rs:612
      anyhow::context::<impl anyhow::Context<T,E> for core::result::Result<T,E>>::context
             at ./root/.cargo/registry/src/github.com-1ecc6299db9ec823/anyhow-1.0.31/src/context.rs:50
      toda::mount::MountsInfo::move_mount
             at src/mount.rs:42
   1: toda::mount_injector::MountInjector::mount
             at src/mount_injector.rs:115
   2: toda::inject
             at src/main.rs:75
      toda::main
             at src/main.rs:139
   3: std::rt::lang_start::{{closure}}
             at ./rustc/16957bd4d3a5377263f76ed74c572aad8e4b7e59/src/libstd/rt.rs:67
   4: std::rt::lang_start_internal::{{closure}}
             at src/libstd/rt.rs:52
      std::panicking::try::do_call
             at src/libstd/panicking.rs:342
      std::panicking::try
             at src/libstd/panicking.rs:319
      std::panic::catch_unwind
             at src/libstd/panic.rs:394
      std::rt::lang_start_internal
             at src/libstd/rt.rs:51
   5: main
   6: <unknown>
   7: _start
@cwen0 cwen0 added the bug Something isn't working label Jan 15, 2021
@cwen0 cwen0 changed the title Some error shouldn't be ignored Some errors shouldn't be ignored Jan 15, 2021
@cwen0 cwen0 changed the title Some errors shouldn't be ignored Mount error shouldn't be ignored Jan 15, 2021
@brutus333
Copy link

Hello! I'm hitting this error but maybe it's a matter of misconfiguration. Please tell me what exactly should I use for path and volumePath while injecting failure into a pod: I used the paths as visible into the pod but maybe my understanding is not correct.

@YangKeao
Copy link
Member

@brutus333 volumePath is the mount path and the path is a glob. For example, if your volumes are mounted at /mnt, and you want to inject chaos for files matching /mnt/some_directory_you_want_to_inject/**/*, you should set volumePath to /mnt and path to /mnt/some_directory_you_want_to_inject/**/*.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants