So, today I was installing recent patches on my firewall box (a Dell
R210-II) using openup/syspatch. After the reboot, it complained that it
couldn't find [DUID].b for swap. After some panic, reboots,
powercycles, etc. I realized that the DUID in fstab didn't match the
DUID that
tly,
> dump -4 is dumping everything again.
>
> Is this simply because /etc/dumpdates deals
> with device names, as opposed to duids?
It sounds like you should start using the -U option on dump starting
with your next level zero for each disk.
I wonder if it could be made the default by
with device names, as opposed to duids?
I ran into this quite awhile ago. My tests definitely confirm dump does
not recognize DUIDs. Many utilities have been made DUID aware, but not
dump(8). Dump reads /etc/dumpdates, which only lists device paths.
This is current/amd64.
After cleaning my machine I reconnected two of my disks in reverse;
what was sd0 is sd1 now, and vice versa.
I do nightly dumps of the filesystems,
starting with level 0 on early Monday morning,
continuing with incremental 1, 2 etc through the week.
Usually this means that
t;> It is a pretty feature. We can start OpenBSD OS from the
>> disk put anywhere(order).
>>
>> But what's about after a dump/restore
>> Boot in
>> single user : backup the disk using 'dump -0af /mnt/root.dump
/dev/wd0a'
> ...
>> How to restore a
the disk using 'dump -0af /mnt/root.dump /dev/wd0a'
...
How to restore a disk using DUID ? keeping duid in
/etc/fstab ?
Thank you very much.
Cheers,
Wesley.
So, you want to restore a disk and magically have the duid of the new
disk assume the old disk's value? I think you haven&#
a on /: No such file or
directory
I suppose DUID is concerned.
To avoid this, i need to modify
/etc/fstab from /dev/wd0a remove DUID use and put the old (cf /dev/wd0a /
...)
Now works...
How to restore a disk using DUID ? keeping duid in
/etc/fstab ?
Thank you very much.
Cheers,
Wesley.
You can mount with duid in fstab but I can't find a way to change root
device to a duid in the boot manual. You must use a device found in
/dev/
http://www.openbsd.org/cgi-bin/man.cgi?query=boot&sektion=8&arch=i386&apropos=0&manpath=OpenBSD+Current
// Johan
2011/10/9 Ji
Hello,
I tried to boot via `bsd -a' and then asked for root device
I wrote DUID of accessible disk but no success.
root device (default sd0a): fba123e4bd29707a.a
use one of: exit em0 iwn0 sd0[a-p] cd0[a-p] sd1[a-p] sd2[a-p]
I still do not understand meaning of this commit, sorry
I don
On Fri, Oct 07, 2011 at 11:49:17PM +1100, Joel Sing wrote:
> On Thursday 06 October 2011, Jiri B wrote:
> > would be possible to tell kernel via `bsd -a' or with extended
> > boot.conf configuration capabilities to use a root device defined
> > with DUID?
>
> Sh
On Thursday 06 October 2011, Jiri B wrote:
> would be possible to tell kernel via `bsd -a' or with extended
> boot.conf configuration capabilities to use a root device defined
> with DUID?
Short answer, no.
> My intend is to boot from an external usb stick and to have root de
It looks it is already possible to have duid for root device:
http://www.openbsd.org/cgi-bin/cvsweb/src/sys/kern/subr_disk.c#rev1.120
I will test during weekend.
jirib
;
I think you don't understand me. I don't want to tell which DUID
should a disk use but to tell kernel to use SUID instead of default
sd0a or a value which one puts when running kernel with `bsd -a'.
jirib
> 2011/10/6 Jiri B :
> > Hello,
> >
> > would be possible t
with extended
> boot.conf configuration capabilities to use a root device defined
> with DUID?
>
> My intend is to boot from an external usb stick and to have root device
> in the box configured with softraid and keydisk.
>
> jirib
Hello,
would be possible to tell kernel via `bsd -a' or with extended
boot.conf configuration capabilities to use a root device defined
with DUID?
My intend is to boot from an external usb stick and to have root device
in the box configured with softraid and keydisk.
jirib
On Sat, 2011-06-25 at 01:57 +1000, Joel Sing wrote:
> On Thursday 02 June 2011, Luca Corti wrote:
> > This is basically a rip off of ntfs_vfsops.c r1.25 and allows the use
> > of DUIDs in fstab for ext2fs.
> Unfortunately, it is a little more complex than this due to the existing
> error handling c
On Thursday 02 June 2011, Luca Corti wrote:
> This is basically a rip off of ntfs_vfsops.c r1.25 and allows the use
> of DUIDs in fstab for ext2fs.
Unfortunately, it is a little more complex than this due to the existing
error handling code. Could you try the following diff?
Index: ext2fs_vfsops.
The convenient thing about mounting your filesystems by DUID in
fstab(5) is that you can just add drives without having to worry
about, say, wd0 becoming wd1 and you having to edit /etc/fstab
correspondingly.
That said, it isn't entirely transparent. If wd0 suddenly does
turn into wd1 an
This is basically a rip off of ntfs_vfsops.c r1.25 and allows the use
of DUIDs in fstab for ext2fs.
Works for me on amd64 GENERIC.MP.
Index: ext2fs_vfsops.c
===
RCS file: /cvs/src/sys/ufs/ext2fs/ext2fs_vfsops.c,v
retrieving revisio
r diskmap,
> I am using it everywhere I can now.
>
> While editing my fstabs, I noticed that some "disks" do not really
> have a DUID; for example the disklabel of my M-Audio Microtrack
> handheld recorder says 'duid: '.
>
> Rereading the man
d that some "disks" do not really
have a DUID; for example the disklabel of my M-Audio Microtrack
handheld recorder says 'duid: '.
Rereading the manpage of disklabel, I see the new feature:
i Change the disklabel UID, specified as a 16-character
21 matches
Mail list logo
