There are a few changes I’ve noticed while poking around the system:
[list][*]It appears we have a quad-core Marvell CPU (3 cores reported; I assume like the FS one core is dedicated to BeyondRAID):
[code]$ cat /proc/cpuinfo
Processor : Marvell PJ4Bv7 Processor rev 2 (v7l)
processor : 0
BogoMIPS : 1196.85
processor : 1
BogoMIPS : 1196.85
processor : 2
BogoMIPS : 1196.85
Features : swp half thumb fastmult vfp edsp vfpv3 tls
CPU implementer : 0x56
CPU architecture: 7
CPU variant : 0x2
CPU part : 0x584
CPU revision : 2
Hardware : Marvell Armada XP Development Board
Revision : 0000
Serial : 0000000000000000[/code]
[*]We have a LOT more memory to play with. Nearly 1GB available to Linux:
$ cat /proc/meminfo | head -1
MemTotal: 880712 kB
[*]Linux kernel is now 3.2; remains to be seen just how said kernel has been configured.
$ uname -a
Linux Drobo 3.2.27 #1 SMP Tue Jan 15 13:57:54 PST 2013 armv7l GNU/Linux
[*]glibc is now updated to 2.11.1
$ /lib/libc.so.6
GNU C Library (EGLIBC) stable release version 2.11.1, by Roland McGrath et al.
Compiled by GNU CC version 4.4.5 20100614 (prerelease).
Compiled on a Linux >>2.6.32-28-server<< system on 2011-06-08.
Available extensions:
crypt add-on version 2.1 by Michael Glad and others
GNU Libidn by Simon Josefsson
Native POSIX Threads Library by Ulrich Drepper et al
Support for some architectures added on, not maintained in glibc core.
BIND-8.2.3-T5B
[*]Still using busybox, but updated to 1.20.2.
BusyBox v1.20.2 (2012-10-05 10:58:47 PDT) multi-call binary.[*]My DroboFS diskpack is mounting as ext4; this is a bit odd since the FS itself used ext3, and I wasn’t aware of any plans to perform an in-place filesystem upgrade. EDIT: According to ricardo, this is likely just backwards-compatible mounting.
$ mount
<snip>
rootfs on / type rootfs (rw)
/dev/root on / type jffs2 (rw,relatime)
proc on /proc type proc (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)
tmpfs on /tmp type tmpfs (rw,relatime)
none on /sys type sysfs (rw,relatime)
/dev/shm on /dev/shm type tmpfs (rw,relatime,size=51200k)
/dev/mtdblock1 on /var type jffs2 (rw,relatime)
/dev/sda1 on /mnt/DroboFS type ext4 (rw,noatime,nodiratime,barrier=1,data=ordered,discard)
[*]No change to the size of the root partition; perhaps more shared memory space:
$ df -h
Filesystem Size Used Available Use% Mounted on
rootfs 30.0M 26.9M 3.1M 90% /
/dev/root 30.0M 26.9M 3.1M 90% /
tmpfs 430.0M 144.0K 429.9M 0% /tmp
/dev/shm 50.0M 256.0K 49.8M 1% /dev/shm
/dev/mtdblock1 3.0M 500.0K 2.5M 16% /var
/dev/sda1 16.0T 4.5T 11.4T 28% /mnt/DroboFS
[*]The diskpack is still mounted at “/mnt/DroboFS”, but “/mnt/DroboNAS” is symlinked to it. There’s a mountpoint for “/mnt/Drobo5N”, which I assume is used for native, non-migrated diskpacks. Nice that we can base everything around a single path, however.
$ ls -l /mnt/
drwxr-xr-x 2 root root 0 Jan 15 13:59 Drobo5N
drwxr-xr-x 7 root root 4096 Jan 18 17:20 DroboFS
lrwxrwxrwx 1 root root 7 Jan 15 13:59 DroboNAS -> DroboFS
[*]They’re definitely laying the groundwork for permissions changes. Everything I’ve seen so far is mapped to user/group of “default:default”. I had to re-chown my home folder before pubkey authentication would work again.[/list]
As I find out more, I’ll post back.
