Displaying 3 results from an estimated 3 matches for "md0a".
Did you mean:
md0
2008 Feb 22
0
mddisk(ramdisk) root system that image size limit ?
...t mfs_root /image // dd if=/dev/zero of=/image bs=1k count=100k
(or count=99k)
}
above config can't boot normal, kernel panic.
[TEST after system up]
1. dd if=/dev/zero of=/image bs=1k count=128k
2. mdconfig -a -t vnode -f /image -u 0
3. bsdlabel -Bw /dev/md0 auto
4. newfs /dev/md0a
5. mount /dev/md0a /mnt
When system up normally: df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/ad0s1a 23G 1.5G 20G 7% /
devfs 1.0K 1.0K 0B 100% /dev
/dev/md0a 124M 4.0K 114M 0% /mnt
system not panic.
but...
2007 Apr 30
3
disk image creation, step by step
...4352 Apr 16 15:44
6.2-RELEASE-i386-bootonly.iso
- Attach this image file as a memory disk:
# mdconfig -a -t vnode -f 6.2-RELEASE-i386-bootonly.img -u 0
- Write a BSD label with boot code to it:
# bsdlabel -w -B md0 auto
- And create a filesystem on it (BSD uses ufs):
# newfs -m 0 md0a
Warning: changing optimization to space because minfree is less than 8%
/dev/md0a: 25.4MB (51984 sectors) block size 16384, fragment size 2048
using 4 cylinder groups of 6.36MB, 407 blks, 832 inodes.
super-block backups (for fsck -b #) at:
160, 13184, 26208, 39232
- Cr...
2006 Mar 15
2
swap at beginning of slice - danger?
Hello freebsd-stable,
I have 5.5-PRERELEASE server in production, booting from ad0s1:
# BLOCKSIZE=512 swapinfo
Device 512-blocks Used Avail Capacity
/dev/ad0s1b 2097152 52872 2044280 3%
/dev/ad1s1b 2097152 51952 2045200 2%
Total 4194304 104824 4089480 2%
# bsdlabel ad0s1 | fgrep b:
b: 2097152 0 swap