Category Archives: FreeBSD

Anything related to FreeBSD

Are one of the disks beginning to fail?

These messages appeared in the kern log file the other day:

Jun 21 22:06:06  enterprise kernel: [282015] (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 18 38 ce 72 40 0b 00 00 00 00 00
Jun 21 22:06:06  enterprise kernel: [282015] (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Jun 21 22:06:06  enterprise kernel: [282015] (ada1:ahcich1:0:0:0): Retrying command
Jun 21 22:06:06  enterprise kernel: [282015] (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 60 58 ce 72 40 0b 00 00 00 00 00
Jun 21 22:06:06  enterprise kernel: [282015] (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Jun 21 22:06:06  enterprise kernel: [282015] (ada1:ahcich1:0:0:0): Retrying command
Jun 21 22:06:06  enterprise kernel: [282015] (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 08 b8 cf 72 40 0b 00 00 00 00 00
Jun 21 22:06:06  enterprise kernel: [282015] (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
Jun 21 22:06:06  enterprise kernel: [282015] (ada1:ahcich1:0:0:0): Retrying command

The disk announces itself as:

ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
ada1: <ST500DM002-1BD142 KC45> ATA-8 SATA 3.x device
ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C)
ada1: quirks=0x1<4K>
ada1: Previously was known as ad6

Elsewhere on the Net I’ve been reading about faulty SATA cables and insufficient power. I doubt the 850 W power supply is to blame, unless there’s a faulty wiring. Maybe it’s a faulty SATA cable. Continue reading Are one of the disks beginning to fail?

Happy nameday, FreeBSD!

FreeBSD is approaching 20 years! I guess it all depends on what you regard as FreeBSD’s true birth. The baptism, the first commit to the CVS repository, the first release, or something else?

The first commit to the CVS repository was done on “Sat Jun 12 14:49:13 1993 UTC”. That’s 20 years and 6 days ago.

On this day, 20 years ago, the name “FreeBSD” was coined by Mr. David Greenman.

Slashdot ran a story on FreeBSD’s 20th birthday, on June 22th, 2013.

On August 28th later this year, I’ll celebrate 15 years of my ever growing experience with this wonderful operating system.

FreeBSD 1.0-RELEASE didn’t appear until November 1st, 1993.

That’s not bad for a free and open source operating system.

By the way, Unix turned 44 years old on April 20th. What’s keeping this big family of operating systems alive when most of their contemporaries have simply gone away?

Making your own FreeBSD Subversion repository mirror

Not long ago it was announced that the FreeBSD ports tree will cease exporting its Subversion repository to CVS, and subsequently any use of CVSup for updating the ports tree will be discontinued by February 28th 2013.

FreeBSD’s main source tree repository has been served by Subversion since late May 2008 with every commit done in the Subversion repository being exported to the old CVS repository, but no date has been announced when that Subversion to CVS transfer will be shut down. Stay tuned for more information.

Nonetheless, this is a Good Time™ to begin the transition from CVSup to Subversion once and for all. And why not set up your own FreeBSD Subversion repository mirror for both the main source tree and the ports tree well ahead of the transition? Continue reading Making your own FreeBSD Subversion repository mirror

When to create a ZFS filesystem?

Someone named “Edward M” posted on the freebsd-questions mailing list a question of when should we create a ZFS filesystem. I didn’t reply to any of the messages, but I decided to write this post expressing my view.

In short, whenever a part of the filesystem hierarchy exhibits different characteristics, create one or more ZFS filesystems for that particular subtree. Continue reading When to create a ZFS filesystem?

endofepoch.c

Jeg børstet støvet av noen tilårskomne filer forleden dag. Jeg fant et lite program som jeg skrev en gang i 2000. Programmet teller ned til slutten av Unix-epoken.

Den opprinnelige definisjonen av datatypen time_t, 32-bit heltall med fortegn, vil få overflyt i midten av januar 2038. Moderne 64-bit OS som FreeBSD/amd64 9.0 har for lengst gått over til 64-bit time_t. Bare ta en titt i fila /usr/src/sys/amd64/include/_types.h, omtrent ved linje 83. Problemet med overflyten i år 2038 vil fortsatt gjelde alt utstyr og (binære) filformater som bruker den gamle definisjonen, slik som FreeBSD/i386 9.0. Ta en titt i fila /usr/src/sys/i386/include/_types.h, omtrent ved linje 91. Den engelske utgaven av Wikipedia har en utfyllende artikkel om problemet.

Kildekoden for det søte, lille programmet mitt, er gjengitt under. Continue reading endofepoch.c