search for: mediasize

I was using a GELI partition for /usr/home on 7.0, so it attaches and mounts on boot. The problem is it stopped working after the system was upgraded to RELENG_7/7.1-PRERELEASE. Here's how it goes: I have the following /etc/fstab: /dev/ad0s1b none swap sw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1d

I have a GPT formatted disk where I recently expanded the size of a partition. I used "gpart resize -i 6 ada1" first to expand the partition to use the remaining free space and then growfs to modify the FFS file system to use the full partition. This was all done in single-user mode, of course, but when I enter "exit" to bring the system up, it failed to mount /usr. This was

...9;t expecting this with 8.3! Are there any quick fixes to eliminate this warning or is it safe to ignore please? sudo gpart list: Geom name: mirror/gm0 modified: false state: CORRUPT fwheads: 255 fwsectors: 63 last: 976773166 first: 63 entries: 4 scheme: MBR Providers: 1. Name: mirror/gm0s1 Mediasize: 500107829760 (465G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 32256 Mode: r2w2e3 attrib: active rawtype: 165 length: 500107829760 offset: 32256 type: freebsd index: 1 end: 976773167 start: 63 Consumers: 1. Name: mirror/gm0 Mediasize: 5001078615...

Hello list, Last night one disk of my desktop machine dead causing a hard lock of the computer. It was a component of a mirror volume so it wasn't as serious as it initially looked. Unfortunately, the metadata structure of my data partition (a geom raid3 array with tree components ) seems to be corrupted by this hard lock, the following message is scrolled constantly on the screen:

...will be a simple server, three users tops. I followed the handbook and made the geli step on the disks: Geom name: label/zfs1.eli State: ACTIVE EncryptionAlgorithm: AES-XTS KeyLength: 128 Crypto: software UsedKey: 0 Flags: NONE KeysAllocated: 38 KeysTotal: 38 Providers: 1. Name: label/zfs1.eli Mediasize: 160041881600 (149G) Sectorsize: 4096 Mode: r1w1e1 Consumers: 1. Name: label/zfs1 Mediasize: 160041885184 (149G) Sectorsize: 512 Mode: r1w1e1 all disks are this way (just 4 disks are on geli zfs). would it be faster, if I had geli over zfs, and not the other way (as is now) ? my...

...c check1 failed ad4: LSI (v3) check1 failed GEOM_MIRROR[2]: Tasting ad4. ad4: LSI (v2) check1 failed magic: GEOM::MIRROR version: 4 name: gm0 mid: 2403671335 did: 1321347210 all: 2 genid: 0 syncid: 1 priority: 0 slice: 4096 balance: round-robin mediasize: 500107861504 sectorsize: 512 syncoffset: 0 mflags: NONE dflags: DIRTY hcprovider: provsize: 500107862016 MD5 hash: fd8b1cfa1aeb685da9b4228f5be3dc41 GEOM_MIRROR[1]: Creating device gm0 (id=2403671335). GEOM_MIRROR[1]: Device gm0 created (2 components, id=2403671335). GEOM_MIRROR[1]: ro...

...ad20 $ graid3 list Geom name: data1 State: COMPLETE Components: 5 Flags: VERIFY GenID: 0 SyncID: 1 ID: 3700500186 Zone64kFailed: 791239 Zone64kRequested: 49197268 Zone16kFailed: 40204 Zone16kRequested: 1283738 Zone4kFailed: 12005939 Zone4kRequested: 2445799003 Providers: 1. Name: raid3/data1 Mediasize: 1280291731456 (1.2T) Sectorsize: 2048 Mode: r1w1e1 ... $ atacontrol list ... ATA channel 6: Master: ad12 <ST3320620AS/3.AAK> Serial ATA v1.0 ATA channel 7: Master: ad14 <ST3320620AS/3.AAK> Serial ATA v1.0 ATA channel 8: Master: ad16 <ST3320620AS/3.AAK> Ser...

...of error 4 lba 30/31 ? - controller is a hp/compaq p400 (ciss) - da0 - da7 are raid0 volumes (controller not jbod capable) - freebsd 9.1 REL (same error message with 9-STABLE from 2013-03-24) - server is zfs-only # diskinfo -v da0 da0 512 # sectorsize 146778685440 # mediasize in bytes (136G) 286677120 # mediasize in sectors 0 # stripesize 0 # stripeoffset 35132 # Cylinders according to firmware. 255 # Heads according to firmware. 32 # Sectors according to...

Hello -STABLE@, So I've seen this situation seemingly randomly on a number of both physical 9.1 boxes as well as VMs for I would say 6-9 months at least. I finally have a physical box here that reproduces it consistently that I can reboot easily (ie; not a production/client server). No matter what I do: reboot shutdown -p shutdown -r This specific server will stop at "All buffers

Hi all, I was intending on trying out gjournal on a new disk i've added in my desktop. I had a look to see what the most recent patch provided by Pawel and found http://people.freebsd.org/~pjd/patches/gjournal6_20061024.patch I created the directories as per Pawel's original post (http://lists.freebsd.org/pipermail/freebsd-fs/2006-June/001962.html) and the patch succeeded with no failed