|
| (Documentation for the Mode=JFS menu) |
|
|
|
|
| DFSee main page | File | Edit | Actions | Display | Help |
| Mode=FDISK | AUX | EXT2+3 | FAT | HFS+ | HPFS | JFS | NTFS | REISER | XFS | SWAP |
Display a pseudo-graphical map of used versus free sectors in the filesystem
Display a usage map for the currently selected disk or filesystem
A pseudo-graphical map of the disk or partition allocation is
displayed, showing the distribution of data over the object
This is also an indication for the amount of unused sectors in
the object, that are beneficial to 'SMART-SECTOR' optimizations
in imaging and cloning operations.
The percentage of used sectors are displayed as a percentage at
the end of the line, and a total usage percentage and size is
shown just after the map itself.
For filesystems that support resizing, the limits for resizing
are shown after the map itself.
Submenu to search for deleted/normal files (no recovery possible yet!)
This submenu offers selections to search for normal or deleted
files, display the resulting lists and possibly recover files.
Note: display of path/filename or recovery is NOT POSSIBLE YET
Search for INODEs for deleted files, 'Recover from list' will UNDELETE them
This will search the whole partition for file INODEs that belong to
DELETED files, and that match the start of the filename specified.
The sectornumbers of the found INODEs will be added to the DFSee
sectorlist so can be used in later actions, or be exported to a file.
The files contained in that list can be RECOVERED to any directory
on the system, including a network, by using the 'RECOVER' command.
Search for INODEs for deleted or non-deleted files, for 'Recover from list'
This will search the whole partition for file INODEs of non-deleted
or deleted files that match the start of the filename specified.
Since this searches the WHOLE filesystem, it is rather SLOW.
For filesystems that are intact, the Quick-Find method should
find ALL normal file inodes too, and is MUCH FASTER!
The sectornumbers of the found INODEs will be added to the DFSee
sectorlist so can be used in later actions, or be exported to a file.
The files contained in that list can be RECOVERED to any directory
on the system, including a network, by using the 'RECOVER' command.
Search data area for INODEs for non-deleted files, for 'Recover from list'
This will search the whole partition for file INODEs of non-deleted
regular files and match the start of the filename specified.
Since this searches the WHOLE filesystem, it is rather SLOW.
For filesystems that are intact, the Quick-Find method should
find ALL normal file inodes too, and is MUCH FASTER!
The sectornumbers of the found INODEs will be added to the DFSee
sectorlist so can be used in later actions, or be exported to a file.
The files contained in that list can be RECOVERED to any directory
on the system, including a network, by using the 'RECOVER' command.
Quick search in INODE areas only for non-deleted files. (fast, QFI command)
This searches JUST the known INODE areas for INODEs of non-deleted
regular files that match the partial filename specified.
The sectornumbers of the found INODEs will be added to the DFSee
sectorlist so can be used in later actions, or be exported to a file.
The files contained in that list can be RECOVERED to any directory
on the system, including a network, by using the 'RECOVER' command.
Note: The filenames to be found are recognizable ONLY when extra
information is available. In DFSee this can be any of:
- Name cache, automatically built with the SLT (and CHECK)
- A .LONGNAME EA set for the file or Dir (June compatible)
- DFSee specific 'magic' names added to the filesystem Inodes
specifically for recovery and undelete. (CHECK -m command)
Quick search in INODE areas only for deleted files. (fast, less effective)
This searches JUST the known INODE areas for INODEs of deleted
files that match the partial filename specified.
This will NOT find all deleted files, since inode-extents will
be discarded completely when many files are deleted. Because of
this, the full search for deleted inodes is recommended.
The sectornumbers of the found INODEs will be added to the DFSee
sectorlist so can be used in later actions, or be exported to a file.
The files contained in that list can be RECOVERED to any directory
on the system, including a network, by using the 'RECOVER' command.
Note: The filenames to be found are recognizable ONLY when extra
information is available. In DFSee this can be any of:
- Name cache, automatically built with the SLT (and CHECK)
- A .LONGNAME EA set for the file or Dir (June compatible)
- DFSee specific 'magic' names added to the filesystem Inodes
specifically for recovery and undelete. (CHECK -m command)
Display (selected) files from the list, using a PATH+FILENAME wildcard
This will display the DFSee sector-list in a compact format, suited
to the data contained in the list
This usually is a 'list -f' or a 'list -s' variant.
Recover (selected) files from the list to a supplied recovery directory
This will allow you to recover (copy) one or more of the files in the
list to any local or network directory on your system.
It will prompt for a destination directory first, using the last used
one as a default. All files recovered in one go, will be recovered to
this same directory, with their original path appended to retain the
directory structure whenever possible.
It will also prompt for a selection specification in the form of a
full PATH+FILENAME wildcard and an optional allocation-percentage.
As an example, the specification:
'*mydoc*\*project_x*.doc%100'
will recover all files that have 'mydoc' somewhere in the PATH,
'project_x' in the filename and have an extension of '.doc' that
seem to be 100% recoverable. (100% allocation-OK ranking).
Recover the file associated with the CURRENT sector to a recovery directory
This will allow you to recover (copy) the file represented by the
CURRENT displayed sector, also called the 'THIS' sector to any local
or network directory on your system.
It will prompt for a destination directory first, using the last used
one as a default. The file will be recovered with its original path
appended to that to retain the directory structure whenever possible.
The menu item will only be enabled (selectable) when the CURRENT sector
represents a normal or deleted FILE for the filesystem involved.
This means it has to be a type 'f' or 'z' sector, which is:
For HPFS: an FNODE sector
For JFS: an INODE sector
For NTFS: an MFT record
Add/Update filenames in the FS, for recovery/undelete (FS must be UNMOUNTED)
This submenu will execute a filesystem check (CHECK/SLT build)
with a special option that instructs it to ADD the found file
and directory names to an unused/reserved area in each INODE.
Since this actually WRITES to the filesystem, it is only effective
when the filesystem is in an UNMOUNTED, CLEAN state.
The added names, when present, will be used to allow display of
filename and full-PATH information, and use these for recovery
and UNDELETE as well.
Note: Filenames displayed in various places for the JFS filesystem
are recognizable ONLY when extra information is available.
(normally it is available in the JFS directories only.)
In DFSee this extra info can be any of:
- Name cache, automatically built with the SLT (and CHECK)
This allows for full path and filenames to be generated
whereever needed, but it DOES require basic JFS structures
to be consistent (not damaged too much).
- A .LONGNAME EA set for the file or Dir (June compatible)
This allows for display of file or directorynames, but not
always a full-path (since the parent directory is unknown)
The mechanism is compatible with the 'June/Jresquer' tools.
- DFSee specific 'magic' names added to the filesystem Inodes
specifically for recovery and undelete. (CHECK -m command)
This allows for full path and filenames to be generated
whereever needed, and does not even require a fully intact
JFS filesystem (some damage tolerated).
Fix bootsector standard/bootable, HiddenSectors/GEO and JFS LDR sectors
This submenu offers selections for fixes related to booting like
fix the bootsector itself, JFS LDR image creation and restore
and fixing the HiddenSectors and geometry fields in the bootsector
This can be very useful when the bootsector got damaged by a virus
or a crashing program (writing to sector 0) or if the partition was
deleted by accident using FDISK or LVM and recreated again.
Create and write STANDARD JFS Bootsector from partition and superblock-info
This will create a new JFS bootsector for the partition, based on
information from the partition-tables and on information found in
the superblock for the filesystem.
This can be very useful when the bootsector got damaged by a virus
or a crashing program (writing to sector 0) or if the partition was
deleted by accident using FDISK or LVM and recreated again.
The bootsector code used is the STANDARD version, as originally
supplied by IBM. JFS partitions using this will not be bootable.
This can be very useful when the bootsector got damaged by a virus
or a crashing program (writing to sector 0) or if the partition was
deleted by accident using FDISK or LVM and recreated again.
Create and write BOOTABLE JFS Bootsector from partition and superblock-info
This will create a new JFS bootsector for the partition, based on
information from the partition-tables and on information found in
the superblock for the filesystem.
This can be very useful when the bootsector got damaged by a virus
or a crashing program (writing to sector 0) or if the partition was
deleted by accident using FDISK or LVM and recreated again.
The bootsector code used is the BOOTABLE version, as supplied with
eComStation 2.x to allow booting from primary or logical JFS.
Apart from ths specific 'bootable' bootsector, you will also need
the JFS mini filesystem (mini-FS) in the sectors directly following
the bootsector itself. If not there yet, you can write that code
using other selections in this same menu.
This can be very useful when the bootsector got damaged by a virus
or a crashing program (writing to sector 0) or if the partition was
deleted by accident using FDISK or LVM and recreated again, or if
the partition was CHKDSK'ed by an OLD non-bootable UJFS.DLL ...
Create compressed imagefile with the JFS LDR sectors for this partition
This will create a compressed imagefile with the JFS mini-FS
sectors from the current JFS partition, to be used later for
a restore to a damaged system.
Restore the imagefile with a 'known good' JFS LDR to current partition
This will restore an imagefile with the JFS mini-FS sectors to
the current JFS partition, to recover from a boot failure when
this code has been damaged somehow ...
Fix bootsector HiddenSectors and geometry fields to match partition tables
This will update the 'hidden sectors' field in the bootsector
to match the offset to the partition-table the partition is
defined in and update the geometry Heads and Sectors field to
match the current disk geometry.
This could be REQUIRED for some operating systems like OS/2
to accept and mount the partition as a driveletter!
Change the volume serial number, making this volume unique (after clone :-)
This will update the 'volume serial number' in the bootsector
This could be REQUIRED for some operating systems after cloning
a filesystem, to make sure the volume serial numbers are unique.
Make the currently selected PRIMARY the 'active' partition for MBR/BIOS boot
This will make the currently selected PRIMARY partition the
ACTIVE one for the disk.
There should only be a single active partition on every disk.
When the system starts, the BIOS will usually boot from
the ACTIVE partition on the first disk.
In IBM BMGR/LVM terms the active partition is called STARTABLE.
Delete the currently selected partition from the partition tables
This will delete the partition that is currently selected to be
deleted from the partition-tables. This will result in the space
occupied by the partition becoming FREESPACE that can be used
again to create new partitions.
For primary partitions on LVM-systems, the related LVM-information
is cleared as well, to avoid consistency problems later when a new
partition is created at the same position.
Update superblock status to indicate filesystem is UNMOUNTED and CLEAN
This will update the fileystem-status field in the JFS superblock
to indicate that filesystem is CLEAN, and not mounted.
This can be useful to avoid an automatic CHKDSK after a system-crash
Note: The filesystem itself is NOT cleaned in any way, it is just the
statusflag that is modified.
Update superblock status to indicate filesystem is DIRTY
This will update the fileystem-status field in the JFS superblock
to indicate that filesystem is DIRTY.
Update superblock status to indicate filesystem is MOUNTED and CLEAN
This will update the fileystem-status field in the JFS superblock
to indicate that filesystem is CLEAN, but IS mounted.
Note: The filesystem itself is NOT cleaned in any way,
it is just the statusflag that is modified.
Display specified Inode sectors or Inode allocation information (IAG)
Display any Inode sector, by specifying the Inode-number
This will display information for the file or directory referenced
by the Inode-sector specified.
This may include filenames, flags, date and time as well as
filespace allocation details.
Note: The Inode-sector has to be identified by its (hexadecimal)
Inode number, as found in directory details or 'well-known'
ones like 02 for the root-directory.
Extension area for the filesystem1 super-inode (Aggregate inode at LSN 68)
Extension area for the filesystem1 super-inode (seldom needed)
It extends the agregate inode at LSN 68, mapping used Inodes
RootDir, main index to the volumes regular files and directories in fileset1
RootDir, main index to the volumes regular files and
directories in fileset1 (the one and only :-)
This is a normal Inode for a directory, but since it is the root
of the directory/file tree, it is the most important one to find
anything by name ...
Special data file with consolidated Access Control List for the fileset
Special data file with consolidated Access Control List for the fileset
Regular file and directory Inodes may contain ACL info that usually
indexes into the data in this file.
Aggregate super or 'self' inode, describing the Aggregate Inode Map blocks
Aggregate 'self' inode, describing the Aggregate Inode Map blocks
Needed to find an aggregate Inode based on its inode number.
Aggregate inode with the bitmap structures that map the whole aggregate
Aggregate inode with the bitmap structures that map the whole aggregate
This systemfile is crucial for displaying the allocation map,
and to determine proper allocation for normal/deleted files
Aggregate inode with blocks allocated to areas detected as 'bad' on format
Aggregate inode with blocks allocated to areas
detected as 'bad' on format
This effectively avoids these blocks from being used for other files
Aggregate inode with the Fileset1 Allocation Map, mapping the Inode extents
Aggregate inode with the Fileset1 Allocation Map,
mapping the Inode extents used for regular inodes
It is needed to allow translation between Inode numbers
and their sector number
Display summary info on all IAG's, or detailed info on a specified IAG nr
Display information about Inode Allocation Groups
Without a number specified, it will list all IAG's
summarizing the number of Inodes per IAG and some
info on the location and inode range used.
With a number specified, the header info for that
IAG structure will be displayed and verified, and
an overview of where the inodes are allocated on disk
Checking the 'verbose' option will cause extra info
to be displayed for the header fields that may allow
repair of a damaged structure.
Checking the 'Aggregate' option will display the info for
the aggregate (system) inodes instead of the fileset-1
(user) ones.
Dump the JFS system areas, Aggr/Fs1 inodes to file for analysis (support :-)
This will create a binary dump for the start of the filesystem
which will include the superblocks and aggregate/fileset inodes.
Quite useful for later analysis, perhaps by DFSee support.
The usual IMAGE dialog will be presented, with the startsector
and size filled in, as well as a suggested filename.
Display the SUPERBLOCK structure for the currently selected filesystem
This will display the contents of the filesystem superblock
in a textual format matching the current filesystem type.
Check filesystem for inconsistencies and errors (Readonly, no fixing!)
This will perform a CHECK of the filesystem, somewhat like the
well-known CHKDSK but without automatically fixing anything.
The result of the check is a sector-lookup-table (SLT) that contains
information about all recognized filesystem areas that are in use.
Any error recognized will be flagged in the default display of
this SLT that is performed automatically by the CHECK command.
Create Sector Lookup Table (SLT) if needed, display as table or sector info
This submenu contains all menu-items related to OPENING an object
to analyse, fix or otherwise work with using other DFSee commands
and menu selections. The opened object will be the CURRENT one.
Show layout of current object by displaying parts of the Sector Lookup Table
This will display part of the sector-lookup-table (SLT)
You wil be presented with an option dialog first, where you
specify the desired format and part of the SLT to be displayed.
The SLT will be built automatically if not done yet, and it will
have been built by any previous CHECK command too.
Building the SLT will take place in the background while the
dialog can be used freely to specify any options for displaying.
After the dialog has been ended, and the SLT is ready, it will
be displayed as requested.
Typically the SLT will contain at least one entry for every file
on the filesystem, so there could be hundreds of thousands lines!
Show identification for specified (or current) sector, using the SLT
This will display information about the specified sector that is
available in the sector lookup table (SLT)
The most useful info is the sector referencing this sector, this
often leads to showing to which file/directory the sector belongs.
The SLT will be generated automatically if not yet available
Show identification for the last sector used, dictating the minimum FS size
This will display information about the sector that is the last
one being used (allocated) in the filesystem, and because of that
dictates the MINIMUM size for the filesystem for a RESIZE.
The most useful info is the sector referencing this sector, this
often leads to showing to which file/directory the sector belongs.
The SLT will be generated automatically if not yet available,
just as the required allocation information (alloc).
Unselect filesystem, reselect the same/first disk; enables Mode=FDISK menu
This will UNSELECT the current object/filesystem, and reselect a
whole physical disk, either the same disk as the partition was on,
or the first disk present in other cases.
This is a quick way to change to 'Mode=FDISK' and work on
disk-level issues
Download the complete menu-documentation as static HTML (15 Mb ZIP)
| DFSee main page | File | Edit | Actions | Display | Help |
| Mode=FDISK | AUX | EXT2+3 | FAT | HFS+ | HPFS | JFS | NTFS | REISER | XFS | SWAP |
| (Mode=JFS page) | DFSee menu documentation for pulldown : Mode=JFS |
| Views: 69473 |
|
Created by Jan van Wijk: Aug 2007, last update: 04-Oct-2007 |
|