@prashks pushed 1 commit.
fdb2855 assertion failed: spa_vdev_remove_thread(): dmu_tx_assign() gets ENOSPC
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://github.com/openzfs/openzfs/pull/482/files/9b12b226e36084d41fc41619a3780567d1353f66..fdb2855b
Ah Gotcha!
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openzfs/openzfs/pull/482#issuecomment-356138925
--
openzfs-developer
Archives:
https://openzfs.topicbox.co
@Skaronator The policy from our legal team is that this should be `, `. I don't know the reasoning
behind that, but it seems several other companies do it this way too, and it
isn't too hard to maintain.
--
You are receiving this because you are subscribed to this thread.
Reply to this email d
Updated my branch to address code review comments and some cstyle/copyright
fixes.
Relevant diffs at:
https://github.com/prashks/illumos-gate/commit/8b37b1da656dd573aba3043a25a8351c6809a0e7
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or vie
@ahrens @avg-l I haven't tested this yet, but I'd be curious to know what y'all
thought about this approach vs. my prior attempts (#507 and #492).
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openzfs/op
PROBLEM
When `dmu_tx_assign` is called from `zil_lwb_write_issue`, it's possible
for either `ERESTART` or `EIO` to be returned.
If `ERESTART` is returned, this will cause an assertion to fail directly
in `zil_lwb_write_issue`, where the code assumes the return value is
`EIO` if `dmu_tx_assign` re
Closed #503.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openzfs/openzfs/pull/503#event-1414268934
--
openzfs-developer
Archives:
https://openzfs.topicbox.com/gr
Closed #502.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openzfs/openzfs/pull/502#event-1414268714
--
openzfs-developer
Archives:
https://openzfs.topicbox.com/gr
Closed #501.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openzfs/openzfs/pull/501#event-1414268510
--
openzfs-developer
Archives:
https://openzfs.topicbox.com/gr
You can view, comment on, or merge this pull request online at:
https://github.com/openzfs/openzfs/pull/513
-- Commit Summary --
* 8930 zfs_zinactive: do not remove the node if the filesystem is readonly
* 8801 loader: always issue our dhcp request
* 8919 loader.efi: remove efi_main() f
Closed #509.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openzfs/openzfs/pull/509#event-1414172491
--
openzfs-developer
Archives:
https://openzfs.topicbox.com/gr
Hi and happy new year :)
I've updated the patch with latest changes from master. If there are no more
comments, can it be merged upstream ?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openzfs/openzfs/
@martymac pushed 1 commit.
29d743b Merge branch 'master' of https://github.com/openzfs/openzfs into
zpool-labelclear-improvements
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://github.com/openzfs/openzfs/pull/424/files/7be4c748e5b99478657b945bb
13 matches
Mail list logo
