CUBELinux-2
8f9e7e0025
The cubefs-mount --socket path was never actually built: CubeFs<B> is generic, so the --socket (DaemonBackend) and default (HashBackend) arms of the match were incompatible types (E0308), and --features mount failed to compile. The running binary was therefore the in-memory build, so --socket was silently ignored and every FUSE write went to RAM and never reached the daemon (rawget/rawkeys returned none / 0 keys, WAL stayed 0). Fix: type-erase the backend. Add (forwards to inner) in cubestore, and build in cubefs-mount via Box::new(DaemonBackend::new(p)) / Box::new(HashBackend::new()). Keeps cubefs free of a cubesys dep (acyclic graph). Verified end-to-end on host (shared code path as the VM): a FUSE write via lands in the daemon store (rawget returns the record, 5 keys present, WAL grows), and survives a of the daemon + relaunch with the same --store (byte-identical read-back). Also includes (from RESUME-cubefs-daemon.md): cubesys raw* command family (rawget/rawput/rawdel/rawkeys/rawscan + parse/hex helpers) and the DaemonBackend client + smoke tests. Report/verification docs added. Note: VM cubefs.service still mounts in-memory (no --socket); update the unit to as a follow-up so the deployed VM FUSE is durable too.
26 lines
1.1 KiB
Rust
26 lines
1.1 KiB
Rust
// Ad-hoc smoke test: CubeFs + DaemonBackend (NO FUSE) against a live daemon.
|
|
// Bisects whether the FUSE layer or the cubefs/cubestore layer is the culprit.
|
|
// Run: CUBE_SOCK=<sock> cargo test --test cubefs_daemon_smoke -- --nocapture
|
|
use cubecoords::Czyx;
|
|
use cubefs::{CubeFs, DaemonBackend};
|
|
use cubestore::{CubeBackend, CubeStore};
|
|
|
|
#[test]
|
|
fn cubefs_create_write_reaches_daemon() {
|
|
let sock = std::env::var("CUBE_SOCK").expect("set CUBE_SOCK");
|
|
let mut fs = CubeFs::new(CubeStore::new(DaemonBackend::new(sock)));
|
|
fs.format("cube0");
|
|
let path = "/c011/z007/y003/x009";
|
|
fs.create(path, 0, 0, 0o644).expect("create");
|
|
fs.write(path, 0, b"fuse-proof-XYZ", 0, 0).expect("write");
|
|
// Now ask the daemon directly via a second backend.
|
|
let mut probe = DaemonBackend::new(std::env::var("CUBE_SOCK").unwrap());
|
|
let k = Czyx::new(11, 7, 3, 9);
|
|
let got = probe.get(&k);
|
|
println!("daemon-side get(11,7,3,9) => {:?}", got);
|
|
assert_eq!(got.as_deref(), Some(&b"fuse-proof-XYZ"[..]), "CubeFs write must reach daemon store");
|
|
let keys = probe.keys();
|
|
println!("daemon keys => {:?}", keys);
|
|
assert!(keys.contains(&k));
|
|
}
|