Opened 7 years ago

Closed 7 months ago

#6764 closed bug (duplicate)

regression, mounting Haiku BFS under Linux fails

Reported by: tqh Owned by: axeld
Priority: normal Milestone: R1
Component: File Systems/BFS Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

I can no longer mount Haiku BFS partition under Linux. It always fails with

Filesystem not clean! There are blocks in the journal. You must boot into BeOS and mount this volume to make it clean. 

Steps to reproduce:

  • jam to a partition.
  • Boot Haiku partition
  • Shutdown Haiku
  • Mount partition under Linux (mount -t befs ...)

Rebooting into Haiku does not help.

Change History (5)

comment:1 Changed 7 years ago by luroh

Fwiw, which is probably not much, I'm unable to repeat this problem on either of my two machines running gcc2 (+ Ubuntu 10.04) and gcc4 (+ Ubuntu 10.10).

comment:2 Changed 6 years ago by axeld

Is that still reproducible? In any case, it doesn't sound like a BFS issue.

BTW did you reboot or actually shut down?

comment:3 Changed 4 years ago by marcm

I've installed hrev45986 gcc2 hybrid via USB-Pendrive on an approx. 11GB partition and stumbled across a fs problem concerning haiku and linux( 3.11.0-3-generic #8-Ubuntu SMP Fri Aug 23 16:52:37 UTC 2013 i686 i686 i686 GNU/Linux)

I cannot mount the haiku Volume on linux

term output:

mount: wrong fs type, bad option, bad superblock on /dev/sda8,

missing codepage or helper program, or other error

syslog(linux): [ 528.178301] BeFS(sda8): No write support. Marking filesystem read-only [ 528.212850] BeFS(sda8): Filesystem not clean! There are blocks in the journal. You must boot into BeOS and mount this volume to make it clean.

It is absolutely reproducable and happens every time i shutdown haiku.

Also it cannot be solved by neither booting Haiku

nor running checkfs.

Starting up from USB-Pendrive and running checkfs on that Volume will get it right.

Here's the output from checkfs:

~> checkfs /dev/disk/scsi/0/0/0/2_3

16567 nodes checked, 0 blocks not allocated, 0 blocks already set, 0 blocks could be freed

files 15343 directories 1074 attributes 77 attr. dirs 58 indices 15

direct block runs 13862 (2.00 GiB) indirect block runs 11 (in 2 array blocks, 472.00 MiB) double indirect block runs 0 (in 0 array blocks, 0 Bytes)

The same haiku-version on the pendrive can be shutdown without showing the error.

comment:4 Changed 4 years ago by marcm

actually it doesn't seem to happen every time i shutdown haiku.

Installed yesterday and this problem occured maybe 6 times in a row.

The last 3 times i shutdown it didn't show up on linux again.

comment:5 Changed 7 months ago by axeld

  • Resolution set to duplicate
  • Status changed from new to closed

It's likely that your system does not shutdown correctly, ie. powers off too early. That would make it a kernel bug, but I believe there already is one for this problem.

Note: See TracTickets for help on using tickets.