Opened 5 years ago
Last modified 5 years ago
#15730 closed bug
Allow delete "bad data" files — at Version 1
| Reported by: | X512 | Owned by: | axeld |
|---|---|---|---|
| Priority: | normal | Milestone: | R1/beta2 |
| Component: | File Systems/BFS | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description (last modified by )
This is hrev53888.
Because of file system corruption "bad data" files appear sometimes. Any attempts to delete such files fails. It should be possible to delete "bad data" files.
Following contents are written to syslog when attempting to delete "bad data" file with rm command:
KERN: bfs: InitCheck:325: Bad data KERN: bfs: KERN: inode at 2881058 is already deleted! KERN: bfs: InitCheck:325: Bad data KERN: bfs: KERN: inode at 2881058 is already deleted!
Problem is likely here: https://xref.landonf.org/source/xref/haiku/src/add-ons/kernel/file_systems/bfs/Inode.cpp#2507. Deletion is refused if opening inode fails. BFS driver should delete file entry in directory even if inode can't be opened.
Note:
See TracTickets
for help on using tickets.
