On Tue, Dec 20, 2011 at 09:51:43AM +1100, Peter Jeremy wrote:
On 2011-Dec-19 22:27:49 +0100, Michiel Boland bolan...@xs4all.nl wrote:
Problem solved - it was indeed an endian thing.
The problem is that fsck uses a real_dev_bsize variable that is declared
long,
but the DIOCGSECTORSIZE ioctl
On Tue, Dec 20, 2011 at 11:48:33AM +0200, Kostik Belousov wrote:
On Tue, Dec 20, 2011 at 09:51:43AM +1100, Peter Jeremy wrote:
On 2011-Dec-19 22:27:49 +0100, Michiel Boland bolan...@xs4all.nl wrote:
Problem solved - it was indeed an endian thing.
The problem is that fsck uses a
Problem solved - it was indeed an endian thing.
The problem is that fsck uses a real_dev_bsize variable that is declared long,
but the DIOCGSECTORSIZE ioctl takes an u_int argument.
A PR has been submitted.
Cheers
Michiel
___
On 2011-Dec-19 22:27:49 +0100, Michiel Boland bolan...@xs4all.nl wrote:
Problem solved - it was indeed an endian thing.
The problem is that fsck uses a real_dev_bsize variable that is declared long,
but the DIOCGSECTORSIZE ioctl takes an u_int argument.
To be accurate, this isn't an endian
FreeBSD 9.0-PRERELEASE locked up while into some heavy I/O and failed to shut
down properly, so I had to power-cycle. After it came back up it said
Starting file system checks:
** SU+J Recovering /dev/ada0a
** Reading 33554432 byte journal from inode 4.
swap_pager: out of swap space
On Dec 17, 2011, at 3:36 PM, Michiel Boland wrote:
FreeBSD 9.0-PRERELEASE locked up while into some heavy I/O and failed to shut
down properly, so I had to power-cycle. After it came back up it said
Starting file system checks:
** SU+J Recovering /dev/ada0a
** Reading 33554432 byte
