mirror of
https://github.com/hanzoai/volume.git
synced 2026-11-03 04:24:40 +00:00
zeekay
b61441f7d7
A fork of Rancher's local-path-provisioner at v0.0.36. The behaviour is unchanged and deliberately so — a directory on the node a pod lands on is the right thing for a disk. What changes is identity. The provisioner answers to hanzo.ai/volume rather than rancher.io/local-path. That is not branding: two provisioners sharing one name race for the same claims, and a stock k3s carries the upstream one, so a cluster running both would settle our storage by chance. Data lives at /var/lib/hanzo/volume, so reading a Hanzo cluster does not mean learning another vendor's directory. Apache-2.0 as published, unaltered, with Rancher's attribution in NOTICE. The README says what this is not: durability. A volume here dies with its node. That is hanzoai/replicate's question, one layer up, and keeping the two apart is what lets the disk stay this simple.
20 lines
705 B
Go
20 lines
705 B
Go
// Copyright 2019 The Go Authors. All rights reserved.
|
|
// Use of this source code is governed by a BSD-style
|
|
// license that can be found in the LICENSE file.
|
|
|
|
//go:build darwin || zos
|
|
|
|
package unix
|
|
|
|
import "unsafe"
|
|
|
|
// ReadDirent reads directory entries from fd and writes them into buf.
|
|
func ReadDirent(fd int, buf []byte) (n int, err error) {
|
|
// Final argument is (basep *uintptr) and the syscall doesn't take nil.
|
|
// 64 bits should be enough. (32 bits isn't even on 386). Since the
|
|
// actual system call is getdirentries64, 64 is a good guess.
|
|
// TODO(rsc): Can we use a single global basep for all calls?
|
|
var base = (*uintptr)(unsafe.Pointer(new(uint64)))
|
|
return Getdirentries(fd, buf, base)
|
|
}
|