Lines Matching refs:you
33 For fault tolerance and raid support (i.e. volume and stripe sets), you can
92 extend the file size so that you can write beyond the existing data. Also,
115 To be sure you are not missing any files, you are
153 files are accessible by name, i.e. you can always do
166 name, if it exists. If case_sensitive, you will need
202 In general use the default. If you have a lot of small
220 problems with this approach so far. If you find a problem with this, please
231 For support of volume and stripe sets, you can either use the kernel's
251 To create the table describing your volume you will need to know each of its
254 For NT4 fault tolerant volumes you can obtain the sizes using fdisk. So for
255 example if one of your partitions is /dev/hda2 you would do:
268 And you would know that /dev/hda2 has a size of 37768814 - 4209030 + 1 =
271 For Win2k and later dynamic disks, you can for example use the ldminfo utility
280 Then you would use ldminfo in dump mode to obtain the necessary information:
285 dynamic disks and all the volumes on them. At the bottom you will see the
286 VOLUME DEFINITIONS section which is all you really need. You may need to look
291 <Disk> components where you will get the LDM Name for the disk that is found in
294 Note you will also need to enable the LDM driver in the Linux kernel. If your
295 distribution did not enable it, you will need to recompile the kernel with it
303 give you the correct information to do this.
305 Assuming you know all your devices and their sizes things are easy.
318 For a striped volume, i.e. raid level 0, you will need to know the chunk size
319 you used when creating the volume. Windows uses 64kiB as the default, so it
320 will probably be this unless you changes the defaults when creating the array.
345 If you are mirroring to multiple devices you can specify further targets at the
350 mirrors are not clean, you can specify the "sync" option instead of "nosync"
352 to the "Target Device" or if you specified multiple target devices to all of
355 Once you have your table, save it in a file somewhere (e.g. /etc/ntfsvolume1),
360 You can obviously replace "myvolume1" with whatever name you like.
362 If it all worked, you will now have the device /dev/device-mapper/myvolume1
363 which you can then just use as an argument to the mount command as usual to
368 (You need to create the directory /mnt/myvol1 first and of course you can use
369 anything you like instead of /mnt/myvol1 as long as it is an existing
381 Software RAID / MD driver. For which you need to set up your /etc/raidtab
386 the MD driver with NTFS volumes" especially if you want to use linear raid).
391 NTFS volume/stripe you are configuring in /etc/raidtab as the persistent
394 Windows by default uses a stripe chunk size of 64k, so you probably want the
397 For example, if you have a stripe set consisting of two partitions /dev/hda5
415 Note for stripe sets with parity you will also need to tell the MD driver
417 which", where you need to replace "which" with the name of the algorithm to
418 use (see man 5 raidtab for available algorithms) and you will have to try the
419 different available algorithms until you find one that works. Make sure you
420 are working read-only when playing with this as you may damage your data
421 otherwise. If you find which algorithm works please let us know (email the
443 one or more sectors so if you mount such a partition with write support you
445 apparent when you try to use the volume again under Windows.
450 Even better is to simply use the Device-Mapper for linear raid and then you do