Hi,
yesterday I rebuilt from latest releng_8 sources a low spec machine running FreeBSD 8.2. Upgrade finished peacefully w/o any trouble. Since the supported zfs version was bumped I upgraded the single pool present and its datasets as follows: zpool v15 -> zpool v28 and zfs v4 -> zfs v5. Just like the core OS those upgraded properly with the respectful messages being issued to confirm that.
However a strange problem arose later when I tried to update some ports software. The sources for those were supposed to download to a zfs fs but instead I saw some complain messages. After having a look into it I found out that all freshly upgraded zfs datasets are in something like a weird readonly state. The pool structure is all intact, all data present and available to read but any write-related operation fails with
error. Although I hadn't changed anything of the working before the upgrade setup, I double-checked all permissions, acls, zfs properties, etc. of the affected datasets and all seems fine. After an export-import combo of the pool the root zfs fs resumed normal operation. I also found out that all newly created zfs sets work like a charm while the upgraded old ones having exactly the same properties "Cannot allocate memory" on write events.
Has anyone had that before or any ideas how to remedy?
The box I run this system on has only 1GB RAM so I know it's low. I followed the zfs tuning guide and have a setup like the low memory example there. So far it worked and like I mentioned above it still does for the new sets.
Cheers
yesterday I rebuilt from latest releng_8 sources a low spec machine running FreeBSD 8.2. Upgrade finished peacefully w/o any trouble. Since the supported zfs version was bumped I upgraded the single pool present and its datasets as follows: zpool v15 -> zpool v28 and zfs v4 -> zfs v5. Just like the core OS those upgraded properly with the respectful messages being issued to confirm that.
However a strange problem arose later when I tried to update some ports software. The sources for those were supposed to download to a zfs fs but instead I saw some complain messages. After having a look into it I found out that all freshly upgraded zfs datasets are in something like a weird readonly state. The pool structure is all intact, all data present and available to read but any write-related operation fails with
Code:
Cannot allocate memory
Has anyone had that before or any ideas how to remedy?
The box I run this system on has only 1GB RAM so I know it's low. I followed the zfs tuning guide and have a setup like the low memory example there. So far it worked and like I mentioned above it still does for the new sets.
Cheers