Displaying 3 results from an estimated 3 matches for "ad4s2".
Did you mean:
ad4s1
2006 Apr 05
1
GEOM_RAID3: Device datos is broken, too few valid components
...ponents ) seems to be corrupted by this hard lock,
the following message is scrolled constantly on the screen:
GEOM_RAID3: Device datos created (id=3217021940).
GEOM_RAID3: Device datos: provider ad6s2 detected.
GEOM_RAID3: Device datos: provider ad5s2 detected.
GEOM_RAID3: Device datos: provider ad4s2 detected.
GEOM_RAID3: Component ad6s2 (device datos) broken, skipping.
GEOM_RAID3: Component ad4s2 (device datos) broken, skipping.
GEOM_RAID3: Device datos is broken, too few valid components.
GEOM_RAID3: Device datos destroyed.
Checking the search engine results it isn't a very usual problem...
2008 Apr 08
4
ZFS deadlock
Hello
A box of mine running RELENG_7_0 and ZFS over a couple of disks (6
disks, 3 mirrors) seems to have gotten stuck. From Ctrl-T:
load: 0.50 cmd: zsh 40188 [zfs:&buf_hash_table.ht_locks[i].ht_lock]
0.02u 0.04s 0% 3404k
load: 0.43 cmd: zsh 40188 [zfs:&buf_hash_table.ht_locks[i].ht_lock]
0.02u 0.04s 0% 3404k
load: 0.10 cmd: zsh 40188 [zfs:&buf_hash_table.ht_locks[i].ht_lock]
2008 Nov 24
2
ext2 inode size patch - RE: PR kern/124621
A while back, I submitted a patch for PR kern/124621, which allows the
mounting of an ext2(3) filesystem created with an inode size other
than 128. The e2fsprogs' default is now 256, so file systems created
on newer Linux distributions or with the port will not be mountable.
I was hopeful this would get committed in time for 7.1-RELEASE (and
6.4-RELEASE), however the PR remains open.
If