Opened 15 years ago
Closed 15 years ago
#4034 closed bug (fixed)
BFS partition became read-only
Reported by: | mmadia | Owned by: | axeld |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | File Systems/BFS | Version: | R1/pre-alpha1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
While using a python build automation script to build Haiku, the partition spontaneously became read-only. The partition is 10GB with about 2GB free. On it is : haiku & buildtools source trees and the generated folder. System is hrev30928-gcc2 and has been up for 1.5days. Attached is syslog. Are there any tests or additional information that would be useful before re-initializing?
/builder> checkfs -c /builder/ haiku-alpha.iso (inode = 2118556), has blocks already set checked 235784 nodes, 0 blocks not allocated, 3072 blocks already set, 3484 blocks could be freed files 186948 directories 48015 attributes 517 attr. dirs 282 indices 22
some snippets from syslog:
KERN: bfs: Remove:1696: No such file or directory KERN: bfs: Could not find value in index "last_modified"! KERN: bfs: Oh no, value 2621458 not found in fragments of node 184320...
KERN: bfs: KERN: double indirect->runs->run: block_run(66, 49596, 4): blocks 4374972 - 4374975 are already set! KERN: bfs: double indirect->runs->run: block_run(66, 49600, 4): blocks 4374976 - 4374979 are already set!
Attachments (1)
Change History (2)
by , 15 years ago
comment:1 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Since the syslog mentions double indirect blocks, I'm closing this one as I fixed a serious error there in hrev31767.