Ext3 on BAFM

USB weirdness

Fri, 08 Aug 2014 09:14:08 +0000

Well, I was at work for a brief moment, where I grabbed me one of our SATA->USB bridges, since I need to migrate some (~750GB) data of the old raid-array and onto a new one. The troublesome about that is simply, that the current RAID controller only supports four attached devices, that’s why I do have to use something like this … Sure I could have bought a new RAID controller, but why spend 45+ EUR on something, that you can solve differently ?

SIL 3114 barfing

Fri, 08 Aug 2014 09:13:36 +0000

Well, after I had so much trouble with the USB converter (which isn’t really suited for Linux), I went ahead and bought a DawiControl DC-154 (which is using a SIL3114) controller to migrate my stuff.

After fucking up the new RAID array with the 1TB disks on the old controller (luckily I had the old hard disks still lying around, which still contained the RAID array), I plugged the 1TB disks onto the new controller and started building the array. So after 760 minutes (that’s nearly 13 hours) of synchronizing the newly created array, I was finally able to create the file system – that should be without trouble, right ?

extfs: Change FS label

Thu, 10 Jan 2013 23:11:54 +0000

`1`	`e2label /dev/md/aggr0 vol1`

MySQL: Beware of sync_binlog on EXT3

Mon, 23 Feb 2009 21:35:38 +0000

Well, I just glazed again over my my.cnf for our web-cluster because I just moved a database from one cluster to another and getting quite different performance from it. So, as I expected, there is a slight difference between both configuration files:

1
2
3
4
5


@@ -55,8 +58,6 @@
 innodb_log_group_home_dir = /var/lib/mysql/db
 innodb_log_file_size = 512M
 innodb_thread_concurrency = 8
-sync_binlog = 1

And apparently, according to the MySQL Performance Blog that’s really, really bad (as well, we’re currently running without write caching, as the battery module of the storage is dead).

Linux: Getting information about an EXT3 filesystem

Fri, 13 Feb 2009 11:52:01 +0000

You know, I’m not getting any younger. It’s getting harder remembering every damn command … so here is how you get information out of your EXT3 filesystem:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10


sles10sp2 ~ [0] > tune2fs -l /dev/sda2 | grep "^Filesystem"
Filesystem volume name: <none>
Filesystem UUID: 8eec8235-4d9e-4b58-acf9-3c68c977d5ea
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal resize_inode filetype
 needs_recovery sparse_super large_file
Filesystem state: clean
Filesystem OS type: Linux
Filesystem created: Tue May 27 10:48:56 2008

MD (Multiple Devices) weirdness

Mon, 29 Dec 2008 17:15:20 +0000

Well, I don’t think my problem has anything to do with the DawiControl card anymore. I did a little experiment today. I created a 1TiB EXT3 file system on a single drive (one of the new 1TiB drives obviously) and started syncing data over to it (roughly 800MiB).

Now, then I unmounted the drive(s), ran fsck -C -f /dev/sd${deviceletter}1 and it went through without any trouble. Then I removed the partition and created a 1GiB partition on each drive, which I then used to build a new device mapper RAID5 array (with EXT3 on top …).