*New 12.1 series Release:
2020-07-21: XigmaNAS 12.1.0.4.7683 - released

*New 11.4 series Release:
2020-07-20: XigmaNAS 11.4.0.4.7682 - released!


We really need "Your" help on XigmaNAS https://translations.launchpad.net/xigmanas translations. Please help today!

Producing and hosting XigmaNAS costs money. Please consider donating for our project so that we can continue to offer you the best.
We need your support! eg: PAYPAL

Why does ZFS|Pools|Management always say there are changes?

Filesystems(UFS, EXT2, FAT, NTFS, ZFS), mount points, partitions
Forum rules
Set-Up GuideFAQsForum Rules
Locked
rcstevensonaz
Starter
Starter
Posts: 20
Joined: 10 Jul 2012 15:58
Status: Offline

Why does ZFS|Pools|Management always say there are changes?

#1

Post by rcstevensonaz »

Whenever I pull up the Disks|ZFS|Pools|Management page, it has the warning box "The configuration has been changed. You must apply the changes in order for them to take effect." But, I have not made any changes... in fact, I am now at the point I have deleted every pool and it still tells me there are changes to be applied every time I enter into that screen.

However, when I click on the Apply changes button, I am given the error message "Error: The changes could not be applied (error code 1)."

When I look in the System log, I do not see any errors logged.

Any ideas?
Last edited by al562 on 24 Dec 2012 05:55, edited 1 time in total.
Reason: Added to FAQs & locked.

rcstevensonaz
Starter
Starter
Posts: 20
Joined: 10 Jul 2012 15:58
Status: Offline

Is this an error in the ZFS Pool creation software?

#2

Post by rcstevensonaz »

I'm looking at the log messages from creating two ZFS pools, and something seems wrong.

Here are the messages from creating first pool (mediap) which looks perfectly normal to me:

Code: Select all

Jul 19 23:33:20 	pelican 	root: Load NOP GEOM class
Jul 19 23:33:21 	pelican 	root: gnop create -S 4096 /dev/ada2
Jul 19 23:33:21 	pelican 	root: gnop create -S 4096 /dev/ada4
Jul 19 23:33:21 	pelican 	kernel: GEOM_NOP: Device ada2.nop created.
Jul 19 23:33:21 	pelican 	root: gnop create -S 4096 /dev/da2
Jul 19 23:33:21 	pelican 	kernel: GEOM_NOP: Device ada4.nop created.
Jul 19 23:33:21 	pelican 	kernel: GEOM_NOP: Device da2.nop created.
Jul 19 23:33:21 	pelican 	root: gnop create -S 4096 /dev/da6
Jul 19 23:33:21 	pelican 	root: zpool create -f -m /mnt/mediap mediap raidz2 /dev/ada2.nop /dev/ada4.nop /dev/da2.nop /dev/da6.nop
Jul 19 23:33:21 	pelican 	kernel: GEOM_NOP: Device da6.nop created.
Then, I go and create the next pool (rootp) which initially looks pretty normal but then appears to be doing something to a disk (ada2) that is part of the the mediap created above:

Code: Select all

Jul 19 23:35:35 	pelican 	root: gnop create -S 4096 /dev/ada0
Jul 19 23:35:35 	pelican 	kernel: GEOM_NOP: Device ada0.nop created.
Jul 19 23:35:36 	pelican 	root: gnop create -S 4096 /dev/da3
Jul 19 23:35:36 	pelican 	root: zpool create -f -m /mnt/rootp rootp mirror /dev/ada0.nop /dev/da3.nop
Jul 19 23:35:36 	pelican 	kernel: GEOM_NOP: Device da3.nop created.
Jul 19 23:35:38 	pelican 	root: gnop create -S 4096 /dev/ada2
Jul 19 23:35:38 	pelican 	root: gnop: Provider ada2.nop already exists.
Any idea what is going wrong?

p.s. also, what are we supposed to do when we find errors in the user interface? Do we mention the issue here on this newbie forum or is there somewhere else where errors should be reported? In this case, the issue is that when you create a ZFS pool, the system should give an error message when you hit submit if you have not selected any virtual devices (like it does when you try to create a vdev without selecting a disk).

User avatar
raulfg3
Site Admin
Site Admin
Posts: 5154
Joined: 22 Jun 2012 22:13
Location: Madrid (ESPAÑA)
Contact:
Status: Offline

Re: Is this an error in the ZFS Pool creation software?

#3

Post by raulfg3 »

Probably the error is due ZFS metadata previosly stored on Disk. Do you reuse / test previosly the disk?.

To avoid problem you need to start from scratch, try to delete / Wipe metadata info . see FAQ 129: http://wiki.nas4free.org/doku.php?id=faq:0129

Do a fresh Install of Nas4Free too to start the creation of your desired pools.

PD: Be patient and wait until nop device is created:
rcstevensonaz wrote:Jul 19 23:33:21 pelican root: gnop create -S 4096 /dev/da6
Jul 19 23:33:21 pelican root: zpool create -f -m /mnt/mediap mediap raidz2 /dev/ada2.nop /dev/ada4.nop /dev/da2.nop /dev/da6.nop
Jul 19 23:33:21 pelican kernel: GEOM_NOP: Device da6.nop created.
12.0.0.4 (revision 6766)+OBI on SUPERMICRO X8SIL-F 8GB of ECC RAM, 12x3TB disk in 3 vdev in RaidZ1 = 32TB Raw size only 22TB usable

Wiki
Last changes

HP T510

rcstevensonaz
Starter
Starter
Posts: 20
Joined: 10 Jul 2012 15:58
Status: Offline

Re: Is this an error in the ZFS Pool creation software?

#4

Post by rcstevensonaz »

raulfg3 wrote:Probably the error is due ZFS metadata previosly stored on Disk. Do you reuse / test previosly the disk?.
Yes, I have been testing with various configurations trying to learn the system. Ugh, seems pretty complicated to deal with. Surprised there is not an easier way to reset disks for ZFS use.

rcstevensonaz
Starter
Starter
Posts: 20
Joined: 10 Jul 2012 15:58
Status: Offline

Re: Why does ZFS|Pools|Management always say there are chang

#5

Post by rcstevensonaz »

So based on comments to a different question I posted, it seems likely that this issue is a result of meta data still on the ZFS disks. I have been doing testing and taking disks in and out of zfs vdevs & pools; and it seems that meta data remains on the drives and creates havoc when trying to reuse the disks.

EDIT UPDATE: When I followed the advise raulfg3 provided (copied below) from another post, my issue has gone a away. Lesson: be very aware of lingering ZFS meta data....
raulfg3 wrote:Probably the error is due ZFS metadata previosly stored on Disk. Do you reuse / test previosly the disk?.

To avoid problem you need to start from scratch, try to delete / Wipe metadata info . see FAQ 129: http://wiki.nas4free.org/doku.php?id=faq:0129
Do a fresh Install of Nas4Free too to start the creation of your desired pools.
PD: Be patient and wait until nop device is created

Locked

Return to “Basic storage concept”