Fix lsblk parsing for filesystem discovery

Remove unused debug code and fix device name parsing to properly handle lsblk tree characters. This resolves the issue where only /boot filesystem was discovered instead of both /boot and /.
Add debug logging for filesystem discovery
2025-11-23 16:09:48 +01:00 · 2025-11-23 15:26:49 +01:00 · 2025-11-23 15:23:15 +01:00 · 2025-11-23 15:15:56 +01:00
6 changed files with 20 additions and 14 deletions
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -279,7 +279,7 @@ checksum = "a1d728cc89cf3aee9ff92b05e62b19ee65a02b5702cff7d5a377e32c6ae29d8d"

 [[package]]
 name = "cm-dashboard"
-version = "0.1.111"
+version = "0.1.116"
 dependencies = [
 "anyhow",
 "chrono",
@@ -301,7 +301,7 @@ dependencies = [

 [[package]]
 name = "cm-dashboard-agent"
-version = "0.1.111"
+version = "0.1.116"
 dependencies = [
 "anyhow",
 "async-trait",
@@ -324,7 +324,7 @@ dependencies = [

 [[package]]
 name = "cm-dashboard-shared"
-version = "0.1.111"
+version = "0.1.116"
 dependencies = [
 "chrono",
 "serde",
--- a/agent/Cargo.toml
+++ b/agent/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "cm-dashboard-agent"
-version = "0.1.112"
+version = "0.1.116"
 edition = "2021"

 [dependencies]
--- a/agent/src/collectors/disk.rs
+++ b/agent/src/collectors/disk.rs
@@ -119,10 +119,7 @@ impl DiskCollector {
            let parts: Vec<&str> = line.split_whitespace().collect();
            if parts.len() >= 2 {
                let device_name = parts[0]
-                    .trim_start_matches('├')
-                    .trim_start_matches('└')
-                    .trim_start_matches('─')
-                    .trim();
+                    .trim_start_matches(&['├', '└', '─', ' '][..]);
                let mount_point = parts[1];
                
                // Skip unwanted mount points
@@ -148,8 +145,13 @@ impl DiskCollector {
        let mut filesystem_usage = HashMap::new();
        
        for mount_point in mount_devices.keys() {
-            if let Ok((total, used)) = self.get_filesystem_info(mount_point) {
-                filesystem_usage.insert(mount_point.clone(), (total, used));
+            match self.get_filesystem_info(mount_point) {
+                Ok((total, used)) => {
+                    filesystem_usage.insert(mount_point.clone(), (total, used));
+                }
+                Err(e) => {
+                    debug!("Failed to get filesystem info for {}: {}", mount_point, e);
+                }
            }
        }
        
--- a/dashboard/Cargo.toml
+++ b/dashboard/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "cm-dashboard"
-version = "0.1.112"
+version = "0.1.116"
 edition = "2021"

 [dependencies]
--- a/dashboard/src/ui/widgets/system.rs
+++ b/dashboard/src/ui/widgets/system.rs
@@ -391,8 +391,12 @@ impl SystemWidget {
                
                for suffix in known_suffixes {
                    if after_fs.ends_with(suffix) {
-                        let fs_name = after_fs[..after_fs.len() - suffix.len() - 1].to_string(); // Remove suffix + underscore
-                        return (Some(fs_name), Some(suffix.to_string()));
+                        // Safely calculate fs_name length
+                        let suffix_with_underscore = suffix.len() + 1;
+                        if after_fs.len() > suffix_with_underscore {
+                            let fs_name = after_fs[..after_fs.len() - suffix_with_underscore].to_string();
+                            return (Some(fs_name), Some(suffix.to_string()));
+                        }
                    }
                }
            }
--- a/shared/Cargo.toml
+++ b/shared/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "cm-dashboard-shared"
-version = "0.1.112"
+version = "0.1.116"
 edition = "2021"

 [dependencies]
Author	SHA1	Message	Date
Christoffer Martinsson	006f27f7d9	Fix lsblk parsing for filesystem discovery All checks were successful Build and Release / build-and-release (push) Successful in 1m9s Details Remove unused debug code and fix device name parsing to properly handle lsblk tree characters. This resolves the issue where only /boot filesystem was discovered instead of both /boot and /.	2025-11-23 16:09:48 +01:00
Christoffer Martinsson	07422cd0a7	Add debug logging for filesystem discovery All checks were successful Build and Release / build-and-release (push) Successful in 1m18s Details	2025-11-23 15:26:49 +01:00
Christoffer Martinsson	de30b80219	Fix filesystem metric parsing bounds error in dashboard All checks were successful Build and Release / build-and-release (push) Successful in 1m8s Details Prevent string slicing panic in extract_filesystem_metric when parsing individual filesystem metrics. This resolves the issue where filesystem entries show —% —GB/—GB instead of actual usage.	2025-11-23 15:23:15 +01:00
Christoffer Martinsson	7d96ca9fad	Fix disk collector filesystem discovery with debug logging All checks were successful Build and Release / build-and-release (push) Successful in 1m9s Details Add debug logging to filesystem usage collection to identify why some mount points are being dropped during discovery. This should resolve the issue where total capacity shows incorrect values.	2025-11-23 15:15:56 +01:00