diff options
| author | Richard Russon <ntfs@flatcap.org> | 2004-11-10 02:03:15 +0000 |
|---|---|---|
| committer | Richard Russon <ntfs@flatcap.org> | 2004-11-10 02:03:15 +0000 |
| commit | aae109deb85d2abb6cebfa0a6e1030d3eca25807 (patch) | |
| tree | 508083f137089493a0119223e3bd31f09e0672bb /Documentation | |
| parent | 3beb711bcfd8c41c171001d6d1f3a3349bb53947 (diff) | |
| parent | bf71a676b90ec6b1ac941b79a98c65378ffe5423 (diff) | |
Merge flatcap.org:/home/flatcap/backup/bk/ntfs-2.6
into flatcap.org:/home/flatcap/backup/bk/ntfs-2.6-devel
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/filesystems/Locking | 4 | ||||
| -rw-r--r-- | Documentation/filesystems/ntfs.txt | 4 |
2 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/filesystems/Locking b/Documentation/filesystems/Locking index 1fd07e10c27e..570ef5db0a07 100644 --- a/Documentation/filesystems/Locking +++ b/Documentation/filesystems/Locking @@ -317,8 +317,8 @@ prototypes: locking rules: called from interrupts. In other words, extreme care is needed here. bh is locked, but that's all warranties we have here. Currently only RAID1, -highmem and fs/buffer.c are providing these. Block devices call this method -upon the IO completion. +highmem, fs/buffer.c, and fs/ntfs/aops.c are providing these. Block devices +call this method upon the IO completion. --------------------------- block_device_operations ----------------------- prototypes: diff --git a/Documentation/filesystems/ntfs.txt b/Documentation/filesystems/ntfs.txt index ad2e32227476..0db4b537af72 100644 --- a/Documentation/filesystems/ntfs.txt +++ b/Documentation/filesystems/ntfs.txt @@ -258,10 +258,10 @@ Then you would use ldminfo in dump mode to obtain the necessary information: $ ./ldminfo --dump /dev/hda This would dump the LDM database found on /dev/hda which describes all of your -dinamic disks and all the volumes on them. At the bottom you will see the +dynamic disks and all the volumes on them. At the bottom you will see the VOLUME DEFINITIONS section which is all you really need. You may need to look further above to determine which of the disks in the volume definitions is -which device in Linux. Hint: Run ldminfo on each of your dinamic disks and +which device in Linux. Hint: Run ldminfo on each of your dynamic disks and look at the Disk Id close to the top of the output for each (the PRIVATE HEADER section). You can then find these Disk Ids in the VBLK DATABASE section in the <Disk> components where you will get the LDM Name for the disk that is found in |