There are no runtime metrics for this change,
This setting may be removed in a future release, Go 1.27 at the earliest.

Go 1.23 changed the mode bits reported by [`os.Lstat`](/pkg/os#Lstat) and [`os.Stat`](/pkg/os#Stat)
for reparse points, which can be controlled with the `winsymlink` setting.
As of Go 1.23 (`winsymlink=1`), mount points no longer have [`os.ModeSymlink`](/pkg/os#ModeSymlink)

pkg syscall (netbsd-arm), type Kevent_t struct, Pad_cgo_0 [4]uint8
pkg syscall (netbsd-arm), type Stat_t struct, Pad_cgo_0 [4]uint8
pkg syscall (netbsd-arm), type Stat_t struct, Pad_cgo_1 [4]uint8
pkg syscall (netbsd-arm), type Stat_t struct, Pad_cgo_2 [4]uint8
pkg syscall (netbsd-arm), type Termios struct
pkg syscall (netbsd-arm), type Termios struct, Cc [20]uint8

pkg syscall (freebsd-arm64), type Stat_t struct, Flags uint32
pkg syscall (freebsd-arm64), type Stat_t struct, Gen uint64
pkg syscall (freebsd-arm64), type Stat_t struct, Gid uint32
pkg syscall (freebsd-arm64), type Stat_t struct, Ino uint64
pkg syscall (freebsd-arm64), type Stat_t struct, Mode uint16
pkg syscall (freebsd-arm64), type Stat_t struct, Mtimespec Timespec
pkg syscall (freebsd-arm64), type Stat_t struct, Nlink uint64

pkg syscall (netbsd-arm64-cgo), type Stat_t struct, Flags uint32
pkg syscall (netbsd-arm64-cgo), type Stat_t struct, Gen uint32
pkg syscall (netbsd-arm64-cgo), type Stat_t struct, Gid uint32
pkg syscall (netbsd-arm64-cgo), type Stat_t struct, Ino uint64
pkg syscall (netbsd-arm64-cgo), type Stat_t struct, Mode uint32
pkg syscall (netbsd-arm64-cgo), type Stat_t struct, Mtimespec Timespec

if err != nil {
 log.Fatalln(err)
}

object, err := os.Open("my-testfile")
if err != nil {
 log.Fatalln(err)
}
defer object.Close()
objectStat, err := object.Stat()
if err != nil {
 log.Fatalln(err)
}

```
mc cp test.file myminio/bucket/
test.file:              5 B / 5 B  ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓  100.00% 337 B/s 0s
```

```
mc stat myminio/bucket/test.file
Name      : test.file
...
Encrypted :
  X-Amz-Server-Side-Encryption: AES256
```

## Encrypted Private Key

pkg syscall (freebsd-riscv64), type Stat_t struct, Flags uint32 #53466
pkg syscall (freebsd-riscv64), type Stat_t struct, Gen uint64 #53466
pkg syscall (freebsd-riscv64), type Stat_t struct, Gid uint32 #53466
pkg syscall (freebsd-riscv64), type Stat_t struct, Ino uint64 #53466
pkg syscall (freebsd-riscv64), type Stat_t struct, Mode uint16 #53466

[issues with the "good first issue" label](https://github.com/tensorflow/tensorflow/labels/good%20first%20issue)
and then take a look at the
[issues with the "contributions welcome" label](https://github.com/tensorflow/tensorflow/labels/stat%3Acontributions%20welcome).
These are issues that we believe are particularly well suited for outside
contributions, often because we probably won't get to them right now. If you

DeleteMarker on the target shows `X-Amz-Replication-Status` of `REPLICA`. The status of DeleteMarker replication is returned by `X-Minio-Replication-DeleteMarker-Status` header on `HEAD/GET` calls for the delete marker version in question - i.e with `mc stat --version-id dm-version-id`

It must be noted that if active-active replication is set up with delete marker replication, there is potential for duplicate delete markers to be created if both source and target concurrently set a Delete Marker...

* Flex drivers by default do not produce metrics. Flex plugins can enable metrics collection by setting  the capability 'supportsMetrics' to true. Make sure the file system can support fs stat to produce metrics in this case. ([#67508](https://github.com/kubernetes/kubernetes/pull/67508), [@brahmaroutu](https://github.com/brahmaroutu))