Tag Info

New answers tagged

0

Quick Definitions: Symbolic link: A link to a file or directory on the same or different volume (drive letter) or even to a remote file or directory (using UNC its path). Hard Link: A link to a file on the same volume (drive letter) only. Junction: A link to a directory on the same or different volume (drive letter) but not to a remote directory. ...


0

Something that works with ZFS for sure, probably also with lvm, btrfs and other volume managers: You could use several empty files (created with dd if=/dev/zero of=file01 bs=1M count=2000) and then use these files as "hard disks" in your volume manager to form a RAID0 (striping). For btrfs and lvm, you have to mount your files as loop devices (see other ...


0

You can transparently access to different parts of file via loops. Below is a script what implements your example setup: dd if=/dev/zero of=A count=8 losetup --offset 0 --sizelimit 1024 /dev/loop0 A losetup --offset 1024 --sizelimit 1024 /dev/loop1 A losetup --offset 2048 --sizelimit 1024 /dev/loop2 A losetup --offset 3072 --sizelimit 1024 /dev/loop3 A ...


0

I also do some research about this question. Here is the results I discovered. The folder size containing hardlinked files in NTFS may be considered in three different meanings: Size including sizes of all hardlinked files (which is shown by WE). Size of unique files only in terms of the current folder. Size of unique files only in terms of the whole ...


2

Windows does indeed support hard links. However, the documentation on CreateHardLink says it all: This function is only supported on the NTFS file system This limitation is probably hard-coded. Because ext2fsd is clearly not NTFS, Windows will refuse to create hard links on it. Cygwin provides POSIX API compatibility (of sorts) on top of Windows APIs. ...



Top 50 recent answers are included