JP2001110169A - Data management methods - Google Patents

Abstract

(57) [Summary] To change the size of an area once defined on a recording medium means to change management information for managing the area. Not only updating the management information that manages the size of the area, but also the above-mentioned FAT and Space Bit that manages the free space in the area
It is necessary to change the map according to the size of the area to be changed, which takes time. A third area acting as a virtual area is created in a first area, management information of this area is recorded in a second area, and a file in the virtual area is stored in the virtual area. Record management information for managing

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an area and data management method when a recording area is secured on a recording medium and data is recorded in the area.

[0002]

2. Description of the Related Art One of the reasons for managing a single disk by dividing it into a plurality of areas is to efficiently record data of different types and properties as described above. For example, there may be a request to manage moving images using a unique logical file system and still images using a FAT file system compliant with the DCF standard, which is widely used in digital cameras and the like.

An area is generally defined at the stage of initializing a disk. When defining a moving image area and a still image area at the time of initialization, how to determine the size of each area is a problem. For example, if the size of the still image area is set too small, the number of still images that can be recorded on this disc decreases, and if the size of the still image area is set too large, a still image is taken at all. Otherwise, the secured area is wasted.

Therefore, it is required to dynamically change the size and the number of the areas in the use process.
For example, the size of an area for recording a still image and an area for recording a moving image is defined by the user at the time of initializing the disc, considering an appropriate size according to the purpose of use. At this time, depending on the file system, the size of the management area of each area can be changed as appropriate. This is because the management information of the file is created in the management area every time one file is created. Therefore, if the management area is small, the number of files to be created is reduced. This is because there is a problem that the area for recording data is reduced. Depending on the file system, the size of the management area may be uniquely determined.

Here, it is considered that a new still image area is defined when the still image area is full. When defining a new area in a state where an area has already been defined, an area on the disk corresponding to the newly defined area must be defined. Since the area on the disk has already been used by the two areas of the moving image and still image, release the unused part of the area on the disk reserved for the moving image area. It must be allocated as a newly defined area. That is, the size of the already defined area is changed.

[0006] Changing the size of an area once defined means that it is necessary to change management information for managing the area. In addition to updating the management information for managing the size of the area, it is necessary to change the above-mentioned FAT or Space Bitmap which manages the free area in the area according to the size of the area to be changed.
Since this is created corresponding to all the logical blocks in the area managed by the FAT and the Space Bitmap, if the number of logical blocks in the area changes, these information must be changed at the same time.

As described above, in order to define a new area, it is necessary to change the management information relating to the already defined area, and there is a problem that it takes time and effort.

[0008] In addition, when the use of adding or deleting an area is considered in a complicated manner, a change in management information that occurs each time an addition or deletion is performed leads to a problem of a decrease in system response.

[0009]

One of the reasons for managing the same disk by dividing it into a plurality of areas is to record data of different types and properties efficiently as described above. . For example, there may be a request to manage moving images using a unique logical file system and still images using a FAT file system compliant with the DCF standard, which is widely used in digital cameras and the like.

[0010] The area is generally defined at the stage of initializing the disk. When defining a moving image area and a still image area at the time of initialization, how to determine the size of each area is a problem. For example, if the size of the still image area is set too small, the number of still images that can be recorded on this disc decreases, and if the size of the still image area is set too large, a still image is taken at all. Otherwise, the secured area is wasted.

Therefore, it is required to dynamically change the size and the number of the areas in the use process.
For example, the size of an area for recording a still image and an area for recording a moving image is defined by the user at the time of initializing the disc, considering an appropriate size according to the purpose of use.

At this time, depending on the file system, the size of the management area in each area can be changed as appropriate. This is because the management information of the file is created in the management area every time one file is created. Therefore, if the management area is small, the number of files to be created is reduced. This is because there is a problem that the area for recording data is reduced. Depending on the file system, the size of the management area may be uniquely determined.

Now, consider defining a new still image area when the still image area is full. When defining a new area in a state where an area has already been defined, an area on the disk corresponding to the newly defined area must be defined. Since the area on the disk has already been used by the two areas of the moving image and still image, release the unused part of the area on the disk reserved for the moving image area. It must be allocated as a newly defined area. That is, the size of the already defined area is changed.

Changing the size of an area once defined means that it is necessary to change management information for managing the area. In addition to updating the management information for managing the size of the area, it is necessary to change the above-mentioned FAT or Space Bitmap which manages the free area in the area according to the size of the area to be changed.
Since this is created corresponding to all the logical blocks in the area managed by the FAT and the Space Bitmap, if the number of logical blocks in the area changes, these information must be changed at the same time.

As described above, in order to newly define an area, it is necessary to change the management information relating to the already defined area, and there is a problem that it takes time and effort.

In addition, when considering the use of adding or deleting an area in a complicated manner, a change in management information that occurs each time an addition or deletion is performed leads to a problem of a decrease in system response.

[0017]

According to the first aspect of the present invention, a first area for recording data is secured on a recording medium, and management information of data recorded in the first area is stored in the first area. In the data management method for recording in a second area in one area, a third area acting as a virtual area is created in the first area, and management information of this area is recorded in the second area. In the virtual area, management information for managing files in the virtual area is recorded.

With this configuration, the virtual area can be managed by the management information of the second area, and setting and deletion of the virtual area can be easily performed. The files in this virtual area are managed by management information recorded in the virtual area. This management information is recorded in a specific area in the virtual area, and may be in a format such as FAT for managing other areas, or may be in any other form.

According to the second aspect of the present invention, the size of the virtual area as the third area is made equal to the size of the external recording medium, and the data of the external recording medium is copied to the third area. Things.

With such a configuration, mutual interchangeability can be easily achieved. The data on the external recording medium is a file and management information for managing the file, and the data is directly copied to a virtual area (third area) of this data size.

According to the third aspect of the present invention, the virtual area is configured as one file. By using the virtual area as one virtual area file, it is possible to easily secure and delete a virtual area as a file using the management information in the second area.

According to the fourth aspect of the present invention, the virtual area is configured as one directory. 1 virtual area
With a directory having two data sizes, the directory can be secured by the management information in the second area,
Deletion can be performed, and files in the virtual area can be managed in the same manner as a normal directory.

[0023]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment relating to a file management method of the present invention will be described below in detail with reference to FIGS. In this embodiment, a video camera using a portable disk as a recording device, video data recorded on the disk is MPEG, and still images are DCF standards (Design rule for Camera) of the Japan Electronics Industry Development Association (JEIDA).
File system). As for the disk device, the present embodiment can be applied as it is even if the stationary video deck or the recording medium is a hard disk or a semiconductor memory.

In the present invention, as an example, a case will be described in which a plurality of data having different properties, that is, a moving image and a still image, are recorded on the same disk. As described above, since video data and still image data having different properties are recorded on the same recording medium, a logical file system suitable for each data is used.

Next, details of the logical file system used in this embodiment will be described. The logical file system manages data recorded on a disk medium in a file format, thereby providing ease of use for a user using the disk or an application program. By designating a file even for data that is divided and recorded at an arbitrary location on a disk, data can be easily read. In addition, the concept of a directory makes it possible to efficiently organize and manage files recorded on a disc.

A disk is generally composed of a set of sectors, and an address is added to each sector. In particular, a sector that can be managed by the logical file system is called a logical sector. In a normal disk, there are areas that cannot be accessed by the logical file system, such as an area for recording parity and an area for a sector used as a substitute when a defect occurs in a sector. The present invention further introduces the concept of a logical block. What is a logical block?
This is a management unit in which 2n (n => 0) logical sectors are collected. The minimum management unit in this logical file system is this logical block. In this description, the size of the logical sector is 2 KB, and the size of the logical block is also 2 KB.

The logical file system described in the present embodiment is divided into management information of a logical file system at a volume level and management information of a logical file system at an area level. FIG. 1 shows a state on a recording medium. Volume
Any number of Areas for specific use can be defined by the management information of the logical file system at the level.
The example of FIG. 1 shows a case where one Area is defined on the recording medium.

In FIG. 1, the entire recording medium is a Volume Spa
ce. In the Volume Space, the area for managing the Volume is the Volume Management Space, and the rest is the Allocatable Space. In this example one
Since one Area is defined in Volume Space, this Allocat
able Space = Area.

The management information for managing Volume is Volume Mana
Recorded in gement Space. In one Volume, an area excluding the Volume Management Space is an Area. In this Volume Management Space, a Primary Volume Descriptor that records basic management information of the entire disk
(PVD), Area Descript to record basic management information of the area
or (AD) is recorded.

The above PVD is the logical sector number 0 of the disk.
(LSN = 0) and logical sector number 16 (LSN = 16) are recorded with the same contents. The PVD recorded in the logical sector 16 is used for backup purpose. P recorded in logical sector 0
Area Descr that manages the basic management information of the disk and the area defined on the disk by accessing the VD
The location where the iptor is recorded can be grasped.

After the logical sector number 32 (LSN = 32) of the area secured as Volume Management Space, Area Descr
iptor is recorded. Area Descriptor is defined Area
Are recorded in the Volume Management Space. The management information of the Area Descriptor is read from the disk based on the information of the PVD. The Area Descriptor makes it possible to grasp the basic information of the Area and the position information of the management information on the disk to be accessed first in the Area.

First, Primary Volume Descriptor (PVD)
The data structure of will be described with reference to FIG. Primary V
The olume Descriptor (PVD) is a management descriptor that records basic management information of the entire disc. PVD includes an ID (Header ID) for identifying the PVD, a type of disk to be managed (Disk Type), and an ID for identifying the disk (DiskI
D), disk size (Volume Size), Allocatable
Space size (Free Logical Sector)
s in Allocatable Space), disk name (Volume Nam
e) PVD creation and modification date (Creation Time & Dat
e, Modified Time & Date), the starting logical sector number and the number of logical sectors (Lo), which are positional information on the disk of the Volume Management Space, which is the management area for managing Area
The start logical sector number and the number of logical sectors (Location of Allocatable Space), which are the location information on the disk of the Allocatable Space that manages the disk area for defining the Area and the Area of Allocatable Space.
Number of Area defined in atable Space
s), Area Desc in which basic information of the defined Area is recorded
The location of the riptor on the disc (Location of Area D
escriptor). In addition, Location of A
The rea Descriptor exists only for the value of Number of Areas. That is, as shown in the example of FIG. 11, when there is only one Area in one Volume, the Location of Area Descrip
tor becomes one.

Here, in the table of FIG. 2, BP is Byte Position
Indicates the start position of the corresponding management item as viewed from the top, Length indicates the size of the management item in bytes, Field Name indicates the management item name, and Contents indicates the format of the management item To indicate if it must be recorded. Of the data types used in Contents,
Uint8 is unsigned 8-bit integer, Uint16 is unsigned 16-bit integer, Uint32 is unsigned 32-bit integer, Uint48 is unsigned 48b
means it integer. String is a data type for storing character strings, and Timestamp is a type for storing date and time information.

As shown in FIG. 3, adr-long in the contents is a data type commonly used in the management descriptor of the present logical file system, and is mainly used as a starting point for arranging data or the like on a disk. Location) and Length. Similarly, as shown in FIG. 4, the Header ID is a data type commonly used in the management descriptor of the present logical file system, and the type of the logical file system (Standard ID),
Logical file system version (Standard Versio
n), the type of management descriptor (Descriptor ID), and the manufacturer (Manufacturer ID) that wrote the management descriptor to the disk.

Next, the data structure of the Area Descriptor (AD) will be described. Area Descriptor (A
D) is a management descriptor that records basic management information of the Area. AD is an ID (Header ID) for identifying AD, Area
(Area Type), the logical block size in the area (Logical Block Size), the size of the area (Area
Size), Area Name (Area Name), AD creation and modification time (Creation Time & Date, Modified Time & Dat
e), a logical block number (Location of Main Primary) which is position information of management information to be accessed first in the Area.
Area Descriptor (PAD), a logical block number (Location of Secondary Primar) which is position information when there is a backup of management information to be accessed first in the Area
y Area Descriptor (PAD)), the number of divisions on the Area disk (Number of Area Extents), the starting logical sector number and the logical sector number (Lo) indicating the position information on the disk for each division
cationof Area Extent). Location of Ar
The ea Extent exists only for the value of the Number of Area Extent. For example, if the Area is composed of two divisions (if the Area consists of two areas), the Location of
There are two Area Extent items, each with its own A
The position information of rea will be recorded.

Next, the structure of data in the area will be described with reference to FIG. The AV Area is divided into an Area Management Space in which management information of the logical file system is recorded and an Extent Space in which the user system records data.

Ar which is a management area of the logical file system
In the ea Management Space, Primary Area Descriptor (PAD), which is management information to be accessed first in the Area,
Space which is management information for managing the free area in rea
A Management Descriptor, a Directory Descriptor which is management information for managing a directory, a File Descriptor for managing an actual file, and the like are recorded.

From the viewpoint of safety, Area Managemen
It is possible to duplicate t Space. When duplexing, the Area Management Space is divided into Main and Secondary areas. The main and secondary areas must have the same contents. When updating the management information, it is necessary to update both areas. In the unlikely event that the management information of Main cannot be read, it is possible to recover the management information by accessing the management area of Secondary.

When accessing the Area, first, the Primary
Read the Area Descriptor (PAD) from the disk. PAD is A
Recorded in logical block number 0 in V Area, Area
Disk with the duplication of the management area, the start position on the disk where the Space Management Descriptor which is the free area management information is recorded, and the Directory Descriptor which manages the root directory, together with the basic information of Information indicating the upper position is provided, and it is possible to read these data.

FIG. 7 shows the structure of a Primary Area Descriptor (PAD). Primary Area Descriptor (PAD) is Area
Is the management information for recording the basic management information. PAD, PAD
(Header ID) to identify the size of Area (Are
a Size), Area Management Sp which is the management area in Area
ace free space (Free Blocks in Area Management Spac
e), the free space of Extent Space (Free Blocks in Extent Space) which is a data area in Area, information indicating Area mode (Area Mode), logical block size in Area (Logical Block Size), Area name ( Area Name), P
AD creation and modification times (Creation Time & Date, Modi
fied Time & Date), start logical block number and logical block number (Lo
cation of Main Area Management Space), the start logical block number and the number of logical blocks (Location of Secondary Area M) which are the position information of the backup management area in the Area
anagement Space), Extent which is the data area in Area
The start logical block number and the number of logical blocks (Location of Extent Space), which are the location information of the Space, and the logical block number (Location of Space), which is the recording start position of the Space Management Descriptor that manages the free area in the Area
Management Descriptor), Direc in the root directory
Logical block number (Location of Root Directory Descriptor) which is the location information where tory Descriptor is recorded
It consists of.

FIG. 8 shows a Space Management Descriptor (SM).
The configuration of D) is shown. The SMD is a management descriptor for managing a free area in the area. SMD is used to identify SMD
ID (Header ID), the logical block number (Next Extension) to be accessed next when the SMD cannot be stored in one logical block and is recorded over a plurality of logical blocks,
Similarly, when a logical block number spans a plurality of logical blocks, the logical block number (Previous Extensio
n) and Space, which is management information for managing free space
Consists of Bitmap. Space Bitmap assigns 1-bit information to all logical blocks in the Area, and if that logical block is used, sets that bit to 1,
If unused, 0 is recorded to manage the free area in the Area.

FIG. 9 shows the structure of the directory descriptor (DD). DD is management information for managing the directory. DD is an ID (Header ID) for identifying the DD, the next logical block number (Next Extension) to be accessed when the DD cannot be stored in one logical block and is recorded over a plurality of logical blocks, and so on. , A logical block number (Previous Extension) in which the previous information is recorded when a plurality of logical blocks are recorded, attribute information of a directory (Attribute), and a directory name (Directory Nam).
e), DD creation and modification time (Creation Time & Dat
e, Modified Time & Date), the logical block number (Pointer to Parent Director) in which the Directory Descriptor of the directory containing the directory to be managed is recorded
y), the starting logical block number and the number of logical blocks (Location of Contiguous Space), which are positional information when managing a continuous area on the disk in a directory structure, and the number of files and directories included in the directory (Number o)
f Descriptor Pointer Entries, pointer information to files and directories contained in the directory (Descri
ptorPointer Entry). Descriptor Pointe
r Entry will have only the value of Number of Descriptor Pointer Entries.

FIG. 10 shows pointer information (Descriptor Pointer E) for files and directories contained in the directory.
ntry). Descriptor Pointer Entry is the name of a file or directory (Entry Name), information for distinguishing whether the managed information is a file or a directory (Entry Type), and positional information where a directory or file management descriptor is recorded. It is composed of a logical block number (Location of Descriptor).

FIG. 11 shows Attr which is directory attribute information.
I will show about ibute. Attribute is 16bit information, B
it0 Read Only indicates whether the managed directory is read-only, Bit1 Deleted indicates whether the managed directory has been temporarily deleted, Bit2 Contiguou
s indicates whether the directory to be managed secures a continuous area on the disk, and Bit3 Allocation Mode is not used for directories, so ZERO is always recorded. Bit4, 5 CGMS (Copy Generation Management System
m) is to allow copying, copy only one generation,
Indicates information on whether to prohibit copying. The Attribute information of the directory has the same configuration as the Attribute in the File Descriptor, which is file management information described later.

A File Descriptor (FD) shown in FIG. 12 is management information of a logical file system for managing a file, and is information handled by a device driver. The FD is an ID (Header ID) for identifying the FD, and when the FD cannot be stored in one logical block and is recorded over a plurality of logical blocks, the logical block number to be accessed next (Next Ext)
extension), a logical block number (Previous) in which the immediately preceding information is recorded when the logical block extends over a plurality of logical blocks.
Extension, file attribute information (Attribute), file name (File Name), creation and modification time of FD (Cre
ation Time & Date, Modified Time & Date), file size (File Size), logical block number (Pointer to Parent Director) indicating the recording position of Directory Descriptor of the directory containing the file to be managed
y), the starting logical block number and the number of logical blocks (Location of Contiguous Extent), which are the position information when managing the continuous area on the disk with the file structure, and the data recorded on the Extent Space managed by the file on the disk (Number of Extents), and the start logical block number and the number of logical blocks (Location of Extent) which are the position information of each division. In addition,
Location of Extent is recorded for the number of divisions managed by Number of Extents.

FIG. 13 shows the attribute information A of the File Descriptor.
Shown about ttribute. Attribute is 16-bit information, Bit0 Read Only indicates whether the managed file is read-only, Bit1 Deleted indicates whether the managed file has been temporarily deleted, Bit2 Contiguous indicates that the managed file is on disk Bit3 Allocation Mode indicates whether the data allocation method managed by the file is an access from the front of the Area or an access from the rear of the Area Bit4, 5 CG
MS (Copy Generation Management System) indicates information as to whether copying is permitted, only one generation is copied, or copying is prohibited. Bits 6 to 15 are reserved for future expansion.

The files and directories recorded in the AV Area can be grasped by tracing from the management information of the root directory. These processes are performed by a device driver that processes according to the logical file system by referring to the management information of the logical file system recorded in the Area Management Space. The disk is accessed using an access command abstracted by specifying the file.

In the present embodiment, a file is actually an Area Management Spac for managing the file.
logical file system management information (File
Descriptor) and actual data corresponding to the file recorded in the Extent Space.

FIG. 14 shows Extended Des which is a descriptor for extension.
It shows about criptor (ED). ED is an ID for identifying the ED
(Header ID), the logical block number (Next Extension) to be accessed next when the ED cannot be stored in one logical block and is recorded across multiple logical blocks, and similarly when the ED spans multiple logical blocks Logical block number (Previous Extension) where the previous information was recorded,
It is configured with a space (Extended Data) for storing information that does not fit in the first logical block.

The management information of the logical file system described above is recorded on the disk in logical block units. Since the size of the logical block is 2KB, for example, the Directory Descriptor that manages one directory and the File Descriptor that manages one file are at least 2KB on disk.
Will be used. If there are few files and directories in the defined directory, use the Directory
Since there are few Descriptor Pointer Entries in the Descriptor, this Directory Descriptor fits in one logical block with a margin. However, if a large number of files and directories are defined in the directory,
Since the scriptor does not fit in one logical block, it must span multiple logical blocks. FIG. 15 shows the Extended Descriptor used in such a situation. In this figure, a certain management descriptor does not fit in one logical block but is recorded over three logical blocks. The first logical block is Directory Desc
If it is a riptor, Descripto could not fit in 2KB
r Pointer Entry information is stored in the second and subsequent logical blocks.
It is managed using Extended Descriptor. Thus E
xtended Descriptor is a container for storing management information with only header information at the beginning, and is a Directory Desc
In addition to the riptor, it is commonly used for management information that must be recorded over a plurality of blocks.

An area managed by the above-described unique logical file system is secured on a disk for recording a moving image. Here, a procedure for creating a video scene recorded on a disc when a user shoots using a video camera or the like will be described.

A series of continuous images from the start of shooting to the stop or the pause are taken as moving image scenes and recorded on the disk as one file. As shown in FIG. 16, a directory “DATA” is created under a root directory to store a file of a video scene to be recorded on a disc.

A file is created for each video scene shot under the directory "DATA". At this time, the file names are determined according to the shooting order, OS0001.MPG, OS0002.MPG, OS000.
3. As in the case of MPG, make it possible to grasp the recording order in the number part. A management unit in which video scenes are combined in accordance with the shooting order is called a program, and here corresponds to the directory “DATA”. In other words, to play from the beginning to the end of the tape like a conventional tape medium, specify the directory "DATA" and play the video scene files saved under that directory in order from OS0001.MPG Thereby, a similar effect can be obtained.

Next, a case where a still image is recorded on the same disk will be described. As described above, since the moving image data has different properties, an area managed based on the FAT file system, which is different from the area where the moving image data is recorded, is defined. Here, the size of an area for recording moving image data and an area for recording a still image poses a problem.

As shown in FIG. 17, in the present invention, the disk 3
In order to record a moving image, the entire area is allocated as the above-described area 2 for the unique file system, and the area for recording still image data is not dared to be defined as in the conventional method. Instead, a file 4 corresponding to an area for recording a still image is created in an area 2 for recording moving image data.

For example, together with a recording medium such as a compact flash which is widely used as a recording medium such as a digital camera, a file 4 corresponding to a virtual area 1 for recording a still image such as 32 MB or 64 MB is used for moving image data. Create in area 2 for recording. At this time, a file for managing the virtual area and a file for managing data of the moving image scene exist in the moving image area.

When a virtual area managed as a file in the area for recording the moving image data is defined, the FAT file system for managing the virtual area for recording the still image is used for managing the area. An initialization process for writing management information and the like is performed. In this way, the virtual area for recording still images is created as a file. If you want to delete this area, simply delete this file in the original file system that simply manages the area for recording moving image data Just complete the process.

As described above, a virtual area for recording still image data is secured in units of 32 MB or 64 MB.
Naturally, when still image data is recorded, it becomes impossible to record a still image any more when the virtual area becomes full.

Therefore, when the virtual area of the still image data becomes full, it is necessary to extend the area of the still image or to define a virtual area for recording new still image data.

In the former, in a unique file system for managing an area for recording moving image data, the size of a file for managing a virtual area for recording still image data is determined by changing the size of a file in the area for recording moving image data. An area is secured by adding the area as an area secured by this file.

In the latter case, a virtual area for recording still image data is newly defined while leaving a virtual area for recording full still image data. In this case, in a unique file system that manages an area for recording moving image data, a free area in the moving image data area is searched to define a file corresponding to a virtual area for still image data. Then, a device driver for the FAT file system that manages a virtual area for recording still image data performs initialization processing on the area.

In this method, for example, if a virtual area for recording still image data is created in units of 32 MB, the upper limit of the capacity that can be recorded in the virtual area is determined. However, by presenting the area in units of 32 MB to the user as an album-like management unit, there is no sense of incongruity. For example, suppose a maximum of 200
Assuming that still images can be recorded, the user can manage up to 200 still images in one album,
Just encourage them to create a new album when they're full. Of course one (of the 32MB unit mentioned above)
Since the album can be classified as an album, the disc area can be used efficiently without the need to create a new album with a new area on the disc unnecessarily.

FIG. 18 shows this state. In the example in this figure,
Files (001, 002, 003, 004) for managing four virtual areas are created in the area for recording moving images.
Each file manages an arbitrary area within the moving image area, and among the managed areas, there is an area managed by the FAT file system. In the example of the figure, the area managed by the file is continuously secured, but this area does not need to be continuously secured, and even if the area is divided in the moving image area. I do not care. Each virtual area file can be accessed as a virtual still image area (file) at the same level as the moving image area.

In this example, each virtual area is regarded as an album such as “travel”, “sports”, “gakugei-kai”, “presentation”, and a user interface as shown in FIG. 19 can be provided. In this example, an album corresponding to each virtual area is displayed on the screen. For example, when an album of “sports” is opened, a still image recorded in the album is displayed as an icon. The still image in the “sports” album is managed by the FAT file system created in the area on the disk managed by the file 002 in the figure. Changing the selected album will
This is the same as changing the virtual area to be accessed, that is, the file to be read.

Further, the size of the virtual area for recording still image data is matched with the capacity of a compact flash or the like (for example, 32 MB or 64 MB) widely used in digital cameras and the like, and the same file system and DCF standard are used. By adopting the file and directory rules based on the above, mutual compatibility can be achieved.

For example, if the recording / reproducing apparatus to which the present invention is applied has means for accessing a recording medium such as the compact flash, the contents of the compact flash can be directly copied to a disk as a virtual area, Thus, the still image virtual area recorded on the disk can be easily copied as it is to the compact flash. The copy here is a simple process such as simple bit-level data transfer, and can be performed very easily. Here, the compact flash is taken as an example, but the object can be achieved with any recording medium as long as it is accessible to the recording / reproducing device. That is, mutual compatibility can be obtained by matching the size of the virtual area with the size of the file system (management information) area and the data area in the recording medium.

In the example of FIG. 20, the entire area of the disk medium 12 accessible from the user system 10 is defined as an area 13 for recording a moving image, and a file 15 for managing a virtual area is created therein. At this time, it seems that the size of the virtual area, the file system, and the like are completely matched with those of the compact flash as the external recording medium 11. As a result, the contents 14 of the external recording medium and the data sequence in the area of the virtual area file 15 are completely compatible, and the contents 14 of the external recording medium can be easily processed in the area of the virtual area file 15 by simple processing. Can be copied just by dumping. Further, by copying the contents of the virtual area file 15 to the compact flash 11 or the like, copying in the reverse direction is enabled. For example, figure
When the contents 14 of the external recording medium are copied to the virtual area at 20, the user system 10 does not access the contents of the external recording medium to the device driver A 16 at a file system level such as a file or a directory, but at the recording medium. The data is read out using a low-level access command for specifying the address of the data and reading out the data recorded there, and the data is transferred to the disk medium to which the data is transferred.
Similarly, data is written by specifying an address by using the low-level access command of the device driver B 17 of the device 12.
At this time, the area in which data is written is an area managed by the virtual area file. By performing such processing for the entire area of the external recording medium, complete copying can be performed.

As described above, in order to create a virtual area managed as a file in an area for recording a moving image, information for recognizing a file as a virtual area is required. One method is to define a file name and a directory name to be recorded as a definition at the user system level. For example, a specific directory is defined in an area managed by a unique file system, a file recorded therein is a virtual area file, and a virtual area having the same file name is created.

Also, in the above-mentioned original file system, a Virtual Area Descriptor is defined as the Volume level management information in the same manner as the Area Descriptor, and this Vi
There is a method to specify the file that manages the virtual area with the rtualArea Descriptor. This Virtual Area Desc
FIG. 21 shows an example of the riptor. This Virtual Area Descrip
The tor is recorded in the Volume Management Space as shown in FIG. This Virtual Area Descriptor is Area Descri
This is management information at the same level as ptor, and can be read and the configuration of the disc can be grasped, for example, when the disc is inserted into the recording / reproducing apparatus targeted by the present invention. As a result, all real and virtual areas defined on the disc can be grasped, and information necessary for actually accessing the respective real and virtual areas can be grasped.

The Virtual Area Descriptor (VAD) is a management descriptor for recording basic management information of a virtual area. VA
D is an ID (Header ID) for identifying VAD, Virtual A
Information indicating the type of file system managing the rea (Virtual Area Type), the size of the Virtual Area (Virtu
al Area Size), the name of the virtual area (Virtual Area Nam)
e), VAD creation and modification time (Creation Time & Dat
e, Modified Time & Date), Area name where virtual area management file is recorded (Virtual Area File Reco)
rded Area Name), the Virtual Area File Recorded Area in which files for managing the Virtual Area are recorded.
Path in the file system in the area of Name (Virtual Ar
ea File Recorded Path), the file name of the file that manages the Virtual Area (Virtual Area File Name), and information (Path to Mount) that is used to make the lower-level file structure of the specified path appear as a virtual area. .

Each time a new virtual area is created, this Virtual Area Descriptor is created.
By referring to this management information, it is possible to grasp the number and types of the defined virtual areas. Virtua
l When defining Area Descriptor, Primary Volume
Virtual A for Descriptor Location of Area Descriptor
The address where the rea Descriptor is recorded is recorded.

FIG. 22 shows the state of the management area at the Volume level when there is a Virtual Area Descriptor. In this example, the entire area of the disc is defined as an area for recording a moving image, which is managed by the Area Descriptor. On the other hand, the virtual area is the Virtual Area Descr
Managed by iptor. Virtual Area Descript
With or, it is possible to specify a real area (Area) including an area of the virtual area on the disk, and to access the disk from a specific file in a file system that manages the real area.

The details of the processing will be described below. For convenience of explanation, the area for recording moving image data is managed by the moving image area, and the moving image area is managed by the above-described unique file system. A device driver for accessing this area is called a unique device driver. An area for recording still image data is managed by a still image virtual area, and a still image virtual area is managed by a FAT file system. A device driver for accessing this area is called a FAT device driver.

The processing procedure for creating a still image virtual area as a file in the moving image area will be described with reference to the flowchart of FIG.

In step S10, when a processing request for newly creating a still image virtual area is generated, the process proceeds to step S11.
In the original device driver that manages the video area, the Space Management Descriptor determines whether there is a free area of the size of the newly created virtual area in the video area.
Search by.

If there is no free area in step S12, error processing is performed in step S19, and the processing ends. In step S12, if there is free space, in step S13, the file management
Record ile Descriptor in Area Management Space.
This File Descriptor manages the position information of the still image virtual area secured in the Extent Space.

In step S14, the Descr of the DirectoryDescriptor of the directory containing the created file
F to manage created files in iptor Pointer Entry
Add pointer information to ileDescriptor and update on disk.

In step S15, Volume Management
The virtual area created in the space, that is, a virtual area descriptor for managing a file serving as the virtual area is recorded. In step S16, the Primary Volume Descriptor is read from the Volume Management Space, and pointer information to the Virtual Area Descriptor that manages the newly created virtual area is added and updated on the disk.

In step S17, the area reserved for the still image virtual area in the Extent Space, the File Descriptor for managing the file, and the Virtual A for managing the virtual area
Space Management Descript corresponding to reaDescriptor
Update or to use status and update on disk.

In step S18, the FAT device driver performs an initialization process on the virtual area secured as a file in the moving image area, and ends the process. The initialization operation means that management information is written in this area so that the area can be used in the FAT file system. FAT device drivers are widely used and can be readily obtained. For example, this can be realized by the user system issuing a FORMAT command to the FAT device driver.

When creating a virtual area of the same size as the external recording medium, it is searched in S11 whether a file of a predetermined size can be created, and a file of the size is created in S13. Then, the processing can be realized by directly dumping the data of the external recording medium to the file which is the virtual area, instead of performing the initialization by the FAT device driver in S18.

FIG. 24 shows a schematic diagram for accessing moving image data and still image data when a still image virtual area is managed as a file in the moving image area. In this figure, the entire area of the disk medium 26 is secured as the moving image area 25, and the user system 20 accesses this moving image area via the device driver B23.

On the other hand, an area for recording a still image is defined as a virtual area 22, and is created as a virtual area file 24 in the moving image area. On the other hand, when the user system 20 accesses a still image in the virtual area 22, the user system 20 accesses the area managed by the virtual area file via the device driver A21. Actually, the user system has 20 device drivers
The position information of the virtual area on the disk is grasped from the management information of the virtual area file via B. Next, the user system 20 accesses, via the device driver A, an area on the disk of the virtual area secured in the grasped moving image area. In the area of the virtual area on the disk, management information and actual data corresponding to the file system accessed by the device driver A are recorded. Diagram of the processing procedure at this time
This will be described with reference to the flowchart of FIG.

When a data access request is generated in step S20, it is determined in step S21 whether or not the access is to a moving image area or a still image virtual area. This can be determined based on whether a virtual area is designated as an area to be accessed. When it is determined in step S21 that the moving image data area is to be accessed, the moving image area is accessed via the unique device driver in step S22.

If it is determined in step S21 that the still image virtual area is to be accessed, the file descriptor of the still image area file managing the still image virtual area is determined in step S23 via the unique device driver.
From the Area Management Space to determine the position information on the disk.

In step S24, a file in the still image virtual area is accessed this time via the FAT device driver in the virtual area. At this time, the position information of the still image virtual area uses the position information acquired in step S23.

As described above, when accessing the still image virtual area, position information is acquired from the File Descriptor of the file that manages the area by the unique device driver, and the subsequent processing is the same as the file processing of the normal FAT file system. There is no change.

In the above embodiment, FIG. 18 and FIG.
The explanation is supplemented with 19 examples. In this case, the Volume Management Space records four Area Descriptors for managing a moving image area and four Virtual Area Descriptors for managing a virtual area for recording a still image. The management information is read when the disc is inserted into the recording / reproducing apparatus, and the configuration of the disc is grasped by the user system. Figure
The application program with the GUI screen as in 19 is based on the information of the read Virtual Area Descriptor, and the icons of "Sports", "Travel", "Gakugei-kai" and "Release event" corresponding to the virtual area where the still image is recorded Is displayed. In this state, for example, when the icon of “sports” is selected and opened by the user, a virtual area corresponding to “sports” is accessed, and a still image in the virtual area is accessed.

The above embodiment is an example of accessing a file system in which a still image is recorded by designating a virtual area. However, when it is desired to directly designate a file name of a still image and display it, the inside of the virtual area is displayed. Creates a file showing the file structure inside the virtual area in the area that records moving images managed by the proprietary file system in order to provide a means to easily grasp the file structure and speed up the search of still image files, etc. You may make it. By reading this file, it is possible to access the still image area after recognizing in which still image area the still image file is recorded.

Next, a still image virtual area is managed as a file in the moving image area, and a processing procedure for expanding the size of the still image virtual area will be described with reference to the flowchart of FIG.

In step S30, when a processing request for expanding the size of the still picture virtual area is issued, step S3
In step 1, the unique device driver that manages the moving image area searches the space area of the moving image area to determine whether or not there is a free area having the size of the area to be expanded. If there is no free area in step S32, error processing is performed in step S38, and the processing ends.

In step S32, if there is a free area, in step S33, the File Descriptor of the file for managing the extended still image virtual area is assigned to the Area Manageme.
Read from nt Space. In step S34, File De
Location of Ex to include the area that the scriptor extends
Update the tent and update on disk. If the number of breakpoints increases, update the Number of Extents as well.

In step S35, the Space Management corresponding to the new area secured for the still image virtual area
Update Descriptor to use status and update on disk. In step S36, a Virtual Area Descrip which manages the virtual area recorded in the Volume Management Space
Update the virtual area size information of tor on the disk.
In step S37, the management information of the still image data area in which the FAT device driver already exists is updated, and the process ends. Specifically, there are management information for managing the size of the area, and reconstruction of the FAT.

The area for recording still image data is managed as a file in the area for recording moving image data.
A processing procedure for reducing the size of the area for recording the still image data will be described with reference to the flowchart in FIG.

In step S40, when a processing request for reducing the size of the still image virtual area is issued,
In S41, the FAT device driver determines whether there is enough free space in the virtual still image area to be reduced. If there is no free area in step S42, error processing is performed in step S48, and the processing ends.

In step S42, if there is a free area, in step S43, the management information of the still image virtual area in which the FAT device driver already exists is updated. Specifically, management information for managing the size of the area,
FAT reconstruction, etc. In step S44, the unique device driver that manages the moving image data area performs File Descrip to manage the still image virtual area as a file.
Read tor from Area ManagementSpace. Step S45
At the location of E of the read File Descriptor
Change the location of the new still image virtual area to be managed by xtents and update on disk. When the number of divisions decreases, the Number of Extents is updated similarly.

In step S46, Volume Management
Virtual Area that manages the virtual area recorded in Space
Update Descriptor information and update on disk. In step S47, the Space Management Descriptor corresponding to the reduced area for the still image virtual area is released and updated on the disk.

A processing procedure for deleting a still image virtual area when a still image virtual area is managed as a file in the moving image area will be described with reference to the flowchart of FIG.

In step S50, when a processing request for deleting the still image virtual area is issued, in step S51, the Primary Volume Desc is deleted from the Volume Management Space.
Virt corresponding to the virtual area to read the riptor and delete
Delete the pointer information to the ual Area Descriptor and update it on the disk. In step S52, the unique device driver that manages the moving image area sets the File Descriptor of the file that manages the still image virtual area to Area Manageme.
Read from the nt Space and grasp the position information of the still image virtual area. In step S53, the still image virtual area to be deleted and the File Descriptor managing the area
And the Virtual AreaDescriptor that managed the virtual area
Release the Space Management Descriptor corresponding to, update on the disk, and end the process.

The case where the still image virtual area is managed as a file in the moving image area has been described.
As a different embodiment, files in the video area
FIG. 29 shows an example in which an access can be made not as a lume-level virtual area but as a virtual directory in a unique file system that manages a moving image area.

In this example, when the user system accesses the virtual directory, the file system in the virtual directory file managed as a file can be accessed. Securing an arbitrary area of the moving image area as a virtual directory and constructing an arbitrary file system for that area is exactly the same as the case of the virtual area described above. In the example of this figure, files (001, 002, 003, 004) for managing four virtual directories in the area for recording moving images
Has been created. Each file manages an arbitrary area within the moving image area, and among the managed areas, there is an area managed by the FAT file system.

In the example shown in the figure, the area managed by the file is continuously secured. However, this area does not need to be continuously secured, and it is an area divided in the moving image area. It does not matter.

Each virtual directory can be accessed as a normal directory when viewed from the user system. In other words, when you enter this virtual directory,
It accesses the file system managed by the virtual directory.

In this example, each virtual directory is regarded as an album such as “travel”, “sports”, “gakugei-kai”, “presentation”, and a user interface as shown in FIG. 19 can be provided. In FIG. 29, when the movement to the “sports” directory, which is a directory in the DATA in the moving image area, occurs, the virtual directory “ The still image file is opened by the file system in "sports", and the still images recorded therein are displayed as icons as shown in FIG.

The still images in the “sports” album are managed by the FAT file system created in the area on the disk managed by the virtual directory “sports” 002 in FIG. Changing the selected album is the same as changing the virtual directory to be accessed. That is, the directory is moved to another directory again by the file system of the moving image area.

In the case of such an embodiment, a Virtual Directory Descriptor is defined as the management information at the Area level in the above-mentioned unique file system. This V
FIG. 30 shows an example of the irtualDirectory Descriptor.

Virtual Directory Descriptor (VDD)
Is a management descriptor for recording basic management information of the virtual directory. VDD is an ID (Header I) for identifying VDD.
D) The logical block number (Next Extension) to be accessed next when VDD cannot be stored in one logical block and is recorded over a plurality of logical blocks, and similarly, one when the VDD extends over a plurality of logical blocks The logical block number (Previous Extension) where the previous information was recorded, and the type of the file system in the virtual directory (Virtual
Directory Type), Virtual Directory Name (Virtual Dire)
ctory Name), VDD creation and modification time (Creation Ti
me & Date, Modified Time & Date), the size of the area managed by the virtual directory (Virtual Directory Siz
e) Specify the logical block number (Pointer to Parent Directory) indicating the recording position of the Directory Descriptor of the directory containing the virtual directory to be managed, specify the file system path in the virtual directory, and virtualize the lower-level file structure from that path. The information to be shown as a directory (Path to Mount), the number of partitions on the disk of the data recorded in the Extent Space managed by the virtual directory (Number of Extents), and the start logical block that is the location information of each partition It consists of a number and the number of logical blocks (Location of Extent). Note that the number of Location of Extents is recorded by the number of divisions managed by the Number of Extents.

Each time a new virtual directory is created, this Virtual Directory Descriptor is created. By accessing this management information, the same effect as accessing the above-described virtual area can be obtained. The creation and deletion of a new Virtual Directory Descriptor can be performed in exactly the same way as adding or deleting a file.
Recorded in Area Management Space in Area.

FIG. 31 shows the state of the area management area when the Virtual Directory Descriptor is recorded. In this figure, the Directory Descriptor that manages the Root directory
Directory Descriptor (DIR Descriptor for D) that manages the DATA directory from (DIR Descriptor for Root)
ATA). Furthermore, DIR Descriptor for D
Virtual Directo manages virtual directories from ATA
The pointer to the ry Descriptor (Virtual DIR Descriptor) has appeared.

From the viewpoint of the user, the normal directory and the virtual directory can be managed in the same manner.
It is possible to access a moving image and a still image without being aware of different device drivers.

Also in this embodiment of the virtual directory, the means for easily grasping the file structure inside the virtual directory is provided, and the file structure inside the virtual directory is shown in order to speed up the retrieval of still image files and the like. The file may be created in an area for recording a moving image managed by a unique file system.

For convenience of explanation, the description has been made on the assumption that an area for recording a moving image and an area for recording a still image.
This is not particularly limited to moving images and still images.If you want to introduce a different file system or if you want to change the area after initialization when dividing and managing the area, this book The invention is applicable.

In the above embodiment, the management information for managing each area is secured in a predetermined single area.
It goes without saying that the management information may be divided into a plurality of areas and recorded.

As described above, an area on the disk is secured by a file structure in a specific area, and the area is treated as a virtual area or directory.
It is possible to solve the problem that was conventionally troublesome when dynamically creating a new area or changing the size. Specifically, when defining a new area or changing the size of a defined area, the area can be achieved by creating, deleting, or changing the size of the file structure. No need to change the size of the area,
Processing will be greatly reduced.

Further, by making the file system and the size in the virtual area or directory the same as those of the compact flash used in the external recording device or the like, mutual data can be easily copied. A highly compatible system can be constructed.

[0116]

According to the present invention, with the above configuration, it is possible to manage a virtual area as a virtual area file or a virtual directory with management information of an upper area (real area). Area setting and deletion can be easily performed. In other words, it is possible to easily manage processing that once required initialization, such as expansion of the area size and release of the area, without initialization.

Further, by making the size of the virtual area the same as the size of the external recording medium, data on the external recording medium can be easily used.

[Brief description of the drawings]

FIG. 1 is an explanatory diagram showing a layout of a disk in a recording medium management method according to an embodiment of the present invention.

FIG. 2 illustrates a recording medium management method according to an embodiment of the present invention.
It is an explanatory view of a Primary Volume Descriptor.

FIG. 3 illustrates a recording medium management method according to an embodiment of the present invention.
FIG. 4 is an explanatory diagram of an adr # long format.

FIG. 4 illustrates a recording medium management method according to an embodiment of the present invention.
It is an explanatory view of a Header ID format.

FIG. 5 illustrates a recording medium management method according to an embodiment of the present invention.
It is explanatory drawing of Area Descriptor.

FIG. 6 illustrates a recording medium management method according to an embodiment of the present invention.
FIG. 3 is an explanatory diagram showing a layout of an AV area.

FIG. 7 illustrates a recording medium management method according to an embodiment of the present invention.
It is explanatory drawing of Primary Area Descriptor.

FIG. 8 shows a recording medium management method according to an embodiment of the present invention.
It is explanatory drawing of Space Management Descriptor.

FIG. 9 illustrates a recording medium management method according to an embodiment of the present invention.
It is an explanatory view of Directory Descriptor.

FIG. 10 is an explanatory diagram of Descriptor Pointer Entry in the embodiment of the recording medium management method of the present invention.

FIG. 11 is an explanatory diagram of a directory attribute in the embodiment of the recording medium management method of the present invention.

FIG. 12 is an explanatory diagram of a file descriptor in the embodiment of the recording medium management method of the present invention.

FIG. 13 is an explanatory diagram of a file attribute in the embodiment of the recording medium management method of the present invention.

FIG. 14 is an explanatory diagram of an Extended Descriptor in the embodiment of the recording medium management method of the present invention.

FIG. 15 is an explanatory diagram showing a method of using an Extended Descriptor in the embodiment of the recording medium management method of the present invention.

FIG. 16 is an explanatory diagram showing how a moving image scene is recorded in the recording medium management method according to the embodiment of the present invention.

FIG. 17 is an explanatory diagram of a relationship between a virtual partition file and a virtual partition file in the embodiment of the recording medium management method of the present invention.

FIG. 18 is an explanatory diagram of a state of a virtual partition file recorded in a moving image partition in the embodiment of the recording medium management method of the present invention.

FIG. 19 is an explanatory diagram showing an example of a user interface in the embodiment of the recording medium management method of the present invention.

FIG. 20 is an explanatory diagram showing how a file for managing a virtual partition is made compatible with an external recording medium in the embodiment of the recording medium management method of the present invention.

FIG. 21 is an explanatory diagram of a virtual area descriptor in the embodiment of the recording medium management method of the present invention.

FIG. 22 is an explanatory diagram showing a disk layout when a Virtual Area Descriptor is introduced in the embodiment of the recording medium management method of the present invention.

FIG. 23 is a flowchart showing a flow of processing for newly creating a virtual partition file in the embodiment of the recording medium management method of the present invention.

FIG. 24 is an explanatory diagram showing a state of a device driver for accessing a moving image partition and a virtual partition in the embodiment of the recording medium management method of the present invention.

FIG. 25 is a flowchart showing a processing flow when a data access request is generated in the embodiment of the recording medium management method of the present invention.

FIG. 26 is a flowchart showing the flow of processing when a request to expand the size of a virtual partition file occurs in the embodiment of the recording medium management method of the present invention.

FIG. 27 is a flowchart showing the flow of processing when a request to reduce the size of a virtual partition file occurs in the embodiment of the recording medium management method of the present invention.

FIG. 28 is a flowchart showing a processing flow when deleting a virtual partition file in the embodiment of the recording medium management method of the present invention.

FIG. 29 is an explanatory diagram showing an outline of a virtual directory which is another embodiment of the recording medium management method of the present invention.

FIG. 30 is an explanatory diagram of a Virtual Directory Descriptor in the embodiment of the recording medium management method of the present invention.

FIG. 31 shows an AV when a Virtual Directory Descriptor is introduced in the embodiment of the recording medium management method of the present invention.
FIG. 3 is an explanatory diagram showing a layout of an Area.

FIG. 32 is an explanatory diagram of how a user system in the related art accesses a disk using management information of a logical file system using a device driver.

FIG. 33 is an explanatory diagram of a case where a plurality of partitions are defined in the related art.

[Explanation of symbols]

 Reference Signs List 20 user system 21 device driver A 22 virtual area 23 device driver B 24 virtual area file 25 video area 26 disk medium

Continued on the front page F term (reference) 5B082 AA13 CA08 CA11 CA17 CA18 EA01 5C052 AA01 AA17 AB03 AB04 AB05 AC08 DD02 DD04 5D110 AA04 AA13 AA29 BB07 BB16 DA01 DA11 DA17 DA20 DB03 DC05 DC16 FA08

Claims (4)

[Claims] A first recording medium for recording data on a first recording medium;
Area, and management information of data recorded in the first area is recorded in a second area in the first area,
A data management method in a recording / reproducing apparatus for managing data in said first area using management information in said second area, wherein a third data area having a predetermined data size is stored in said first area. And the management information of the third area is recorded in the second area, and the management information of the data recorded in the third area is recorded in the third area. Management information recorded in the area 3 and the second
A data management method for managing data in the third area by using management information in the area. 2. An area is secured by setting the data size of the third area equal to the size on a second recording medium different from the first recording medium. 2. The data management method according to claim 1, wherein data is copied to a third area in the first recording medium. 3. Management information for managing the entire recording medium is stored in a fourth storage medium.
No. 1 to record on the recording medium and record data on the recording medium
Area, and the management information of the first area is stored in the fourth area.
And recording management information of a file recorded in the first area in a second area in the first area,
A data management method in a recording / reproducing apparatus for managing files in said first area using management information in said second area, comprising: a virtual area having a predetermined data size in said first area. Creating a file, recording management information of the virtual area file in the second area, recording management information of data recorded in the virtual area file in the virtual area file, Using the management information and the management information in the second area, manage data in the virtual area file, and manage the virtual area file as a virtual area and the virtual area file as a virtual area. The management information of the virtual area including the information specifying the virtual area file is recorded in the fourth area, and the management information of the virtual area is recorded. Data management method and performing. 4. A first area for recording data on a recording medium is secured, and management information of data recorded in the first area is recorded in a second area in the first area. A data management method in a recording / reproducing apparatus for managing data in a first area using management information in a second area, wherein the first area has an area of a predetermined data size. Creating a virtual directory, recording management information of the virtual directory in the second area, recording management information of data recorded in the virtual directory in an area secured as the virtual directory, Directory and management information in the area and the second
A data management method for managing data in said virtual directory using management information in said area.