| Summary: | sys-fs/e4rat-0.2.3-r1 - e4rat-realloc: Cannot open file: /sys/fs/ext4/dm-N/mb_stream_req | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Norman Back <gentoo3> |
| Component: | [OLD] Core system | Assignee: | Pacho Ramos <pacho> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Norman Back
2013-12-19 12:04:38 UTC
Full output from e4rat-realloc. e4rat-realloc /var/lib/e4rat/startup.log Parsing file /var/lib/e4rat/startup.log 2/3774 file(s) are not available 56/3774 file(s) are presently not writable. 5/3774 file(s) have no blocks. 1/3774 file(s) are sparse-files which will retain gaps of unallocated blocks. Defrag mode: locality group Processing 702 file(s) on device /dev/dm-0 (mount-point: /) Total fragment count before/afterwards/best-case: 153/59/1 Processing 63 file(s) on device /dev/dm-1 (mount-point: /opt) Total fragment count before/afterwards/best-case: 23/25/1 There is no improvement possible. Processing 132 file(s) on device /dev/dm-2 (mount-point: /var/tmp) Total fragment count before/afterwards/best-case: 18/10/1 Processing 1 file(s) on device /dev/dm-4 (mount-point: /var/log) Total fragment count before/afterwards/best-case: 1/1/1 There is no improvement possible. Processing 2448 file(s) on device /dev/dm-5 (mount-point: /usr) Total fragment count before/afterwards/best-case: 91/71/1 Processing 365 file(s) on device /dev/dm-8 (mount-point: /home/norman) Cannot open file: /sys/fs/ext4/dm-8/mb_stream_req Cannot dump log messages: /dev/kmsg: Bad file descriptor Discard 3 unwritten log message(s). Please create a bug in upstream site: https://sourceforge.net/p/e4rat/tickets/new/ And post the link here to let me track the issue there Thanks! (In reply to Pacho Ramos from comment #2) > Please create a bug in upstream site: > https://sourceforge.net/p/e4rat/tickets/new/ > > And post the link here to let me track the issue there > > Thanks! I have attempted to reproduce the error but it has gone away, most likely due to a kernel upgrade. OK, will see if it was solved then :/ |
