Coronation and Linux

This weekend was the coronation of King Charles III, the first new monarch for most of the people in the UK. Some may have been alive for the late Queen Elizabeth II’s coronation but the are few now.

I was working coronation support cover on the Saturday from around 6:30am to about 3pm. Fortunately no major issues. One alert towards the tail end of the day, but that was about it.

Sunday were the street parties. Our local one was relatively small compared to the one during the Jubilee celebrations. Was great for the local kids though, and the weather was perfect for it.


Monday is a Bank Holiday so no-one was working in the London office, although the other offices were still working.

I chose today to retry doing my Manjaro file copy, and again it failed with checksum errors when I tried to back it up (even the btrfs check didn’t manage to fix it)

I guess I’ll have to restart my Manjaro attempts and not use btrfs — probably return to using ext4 and lvm.

Manjaro

I’ve been continuing to tinker with ArchLinux and Manjaro and have since found out about “Oh-My-Zsh” and “Oh-My-Bash” — basically addons you can add onto your shell via the shell’s rc and profile files and it provides a really nice prompt that tells you additional information at a glance, like which branch you are in if you are in a git repo, or whether the previous command returned a non-zero error code.

They are quite polarising though, as I found out when I mentioned this to one of the systems architects here in the office. One of the architects told me someone he worked with even considered OMZ malware.

Vanilla ArchLinux uses bash out of the box, Manjaro uses zsh out of the box, which is how I found out about the OMZ/OMB addons.

OMZ has a ton more plugins than OMB – unsurprisingly since it’s also the default shell for Macs (vomit).

I did start copying my files across to my Manjaro installation. It took nearly 6 hours to copy. However, when trying to do the backup afterwards, it failed with a btrfs checksum error. That worried me since I hadn’t done anything since the previous backup other than copying files.

I do remember running into similar issues with btrfs last time I tinkered with it when reinstalling Fedora. It could end up with me switching to either ext4 (like I did with Fedora) or trying the xfs file system option in Manjaro.

Corporate Linux

Virtualization madness

Had my first encounter of Linux, or specifically, a linux-like environment in a corporate environment. The IT peops were trying to setup an environment on Xenserver, and they had setup a storage space to copy a virtual machine image onto. But they kept running out of space. It took me a while to figure out what they were doing (wrong), though.

They were trying to copy onto the PV partition, and Xenserver had setup its environment to use LVM, so the PV partition was already allocated to the LVM system, and therefore had no space to copy onto.

After figuring out which LV was the one they wanted to use, I had problems mounting, with mount saying I had to specify the filesystem. After trying various switches with mount and specifying a filesystem (only NFS, ext, ext2 and ext3 were supported by Xenserver. No vfat, ntfs or btrfs. Admittedly, however, the Xenserver version the IT people were using was an older version), I soon found out that the IT people had created the storage space, but not done anything else. Therefore, that would explain why I couldn’t mount it — it hadn’t been formatted. So a simple mkfs.ext3 (remember ext4 wasn’t supported) on the block device in /dev/mapper/ meant I could mount it without specifying filesystem. scp’ing into the server and copying into the path proved it worked.

 

%d bloggers like this: