IP Library Granted Patent US 9,411,526
Granted Patent B1
US 9,411,526 · App. 14/616,756 · Granted Aug 9, 2016

Filesystem management

Inventors: Jacob Broido (Tel-Aviv, IL); Eran Brown (Givatayim, IL)
Assignee: INFINIDAT LTD.
G06F3/0619G06F3/065G06F3/067G06F3/0643G06F17/30G06F17/30091
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,411,526
App. No.
14/616,756
Granted
Aug 9, 2016
Kind
B1
Abstract

A method for managing a filesystem by a storage system, the method may include maintaining, by a storage system, a filesystem data structure that comprises filesystem pathnames metadata related to a filesystem that is stored in the storage system; receiving, from a client that is coupled to the storage system via a network, a request to obtain a client filesystem object list related to at least a certain portion of the filesystem; generating, in response to the request and in response to the filesystem data structure, the client filesystem object list, wherein the client filesystem object list comprises at least one pathname of at least one filesystem object that belongs to the at least certain portion of the filesystem; and sending the client filesystem object list to the client.

Claims (20)

1. A method for managing a filesystem by a storage system, the method comprises:

maintaining, by a storage system, a filesystem data structure that comprises filesystem pathnames metadata related to a filesystem that is stored in the storage system;

receiving, from a client that is coupled to the storage system via a network, a request to obtain a client filesystem object list related to at least a certain portion of the filesystem;

generating, in response to the request and in response to the filesystem data structure, the client filesystem object list, wherein the client filesystem object list comprises at least one pathname of at least one filesystem object that belongs to the at least certain portion of the filesystem; and

sending the client filesystem object list to the client.

2. The method according to claim 1 wherein the filesystem pathnames metadata comprises pathnames of filesystem objects that belong to the filesystem.

3. The method according to claim 1 wherein the filesystem pathnames metadata comprises pathname retrieval information that facilitates a retrieval of pathnames of filesystem objects that belong to the filesystem.

4. The method according to claim 1 wherein the filesystem data structure further comprises filesystem attribute metadata that differs from the filesystem pathnames metadata.

5. The method according to claim 4 wherein the filesystem attribute metadata comprises attributes of filesystem objects that belong to the filesystem.

6. The method according to claim 5 wherein an attribute of a filesystem object of the filesystem objects that belongs to the filesystem is a size of the filesystem object.

7. The method according to claim 5 wherein an attribute of a filesystem object of the filesystem objects that belongs to the filesystem is a timestamp related to an operation applied on the filesystem object.

8. The method according to claim 4 wherein the filesystem attribute metadata comprises attributes retrieval information that facilitates a retrieval of attributes of filesystem objects that belong to the filesystem.

9. The method according to claim 1 wherein the generating of the client filesystem object list is responsive to client access permissions related to filesystem objects that belong to the at least certain portion of the filesystem.

10. The method according to claim 1 wherein the request to obtain the client filesystem object list comprises a predefined term that represents the client filesystem object list.

11. The method according to claim 1 comprising storing, in a certain location in the filesystem, an executable file that once executed by the client causes the client to respond to the request to obtain the client filesystem object list related to the at least certain portion of the filesystem by generating the client filesystem object list.

12. The method according to claim 1 wherein the maintaining comprises updating in real time the filesystem data structure in response to any change in the filesystem that mandates a change in the content of the filesystem data structure.

13. The method according to claim 1 wherein the maintaining comprises updating in real time the filesystem data structure in response to an addition of any filesystem object to the filesystem, a deletion of any filesystem object of the filesystem, a renaming of any filesystem object of the filesystem and a moving of any file system object of the filesystem.

14. The method according to claim 1 wherein the request is a network-attached storage (NAS) storage read request.

15. A non-transitory computer readable medium that stores instructions that once executed by a storage system causes the storage system to executed the stages of: maintain a filesystem data structure that comprises filesystem pathnames metadata related to a filesystem that is stored in the storage system; receive, from a client that is coupled to the storage system via a network, a request to obtain a client filesystem object list related to at least a certain portion of the filesystem; generate, in response to the request and in response to the filesystem data structure, the client filesystem object list, wherein the client filesystem object list comprises at least one pathname of at least one filesystem object that belongs to the at least certain portion of the filesystem; and send the client filesystem object list to the client.

16. A storage system comprising a controller and an interface, wherein the controller is configured to maintain a filesystem data structure that comprises filesystem pathnames metadata related to a filesystem that is stored in the storage system; wherein the interface is configured to receive, from a client that is coupled to the storage system via a network, a request to obtain a client filesystem object list related to at least a certain portion of the filesystem; wherein the controller is configured to generate, in response to the request and in response to the filesystem data structure, the client filesystem object list, wherein the client filesystem object list comprises at least one pathname of at least one filesystem object that belongs to the at least certain portion of the filesystem; and wherein the interface is configured to send the client filesystem object list to the client.

Assignments (8)
SECURITY INTEREST Recorded Jan 30, 2025
From: INFINIDAT LTD
To: KREOS CAPITAL VII AGGREGATOR SCSP,
Reel/Frame 070056/0458 →
RELEASE OF SECURITY INTEREST IN IP RECORDED AT R/F 55653/0854 Recorded Jan 18, 2024
From: SILICON VALLEY BANK
To: INFINIDAT LTD.
Reel/Frame 066344/0064 →
SECURITY INTEREST Recorded Jan 11, 2024
From: INFINIDAT LTD
To: KREOS CAPITAL VI (EXPERT FUND) L.P.; KREOS CAPITAL 2020 OPPORTUNITY L.P.
Reel/Frame 066270/0359 →
SECURITY INTEREST Recorded Jan 10, 2024
From: INFINIDAT LTD
To: HSBC BANK PLC
Reel/Frame 066268/0584 →
RELEASE OF SECURITY INTEREST Recorded Mar 30, 2021
From: BANK LEUMI LE-ISRAEL B.M.
To: INFINIDAT LTD.
Reel/Frame 055776/0526 →
SECURITY INTEREST Recorded Mar 18, 2021
From: INFINIDAT LTD.
To: SILICON VALLEY BANK
Reel/Frame 055653/0854 →
SECURITY INTEREST Recorded Apr 12, 2018
From: INFINIDAT LTD.
To: BANK LEUMI LE-ISRAEL B.M.
Reel/Frame 045914/0276 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 12, 2015
From: BROIDO, JACOB; BROWN, ERAN
To: INFINIDAT LTD.
Reel/Frame 034944/0393 →